Triple
T9281994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .xk |
E223090
|
entity |
| Predicate | usedInformallyOn |
P70028
|
FINISHED |
| Object | internet |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: internet | Statement: [.xk, usedInformallyOn, internet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInformallyOn Context triple: [.xk, usedInformallyOn, internet]
-
A.
usedInformallyAlongside
Indicates that something is employed in an informal, non-standard way together with or in addition to something else.
-
B.
hasInformalUsage
chosen
Indicates that something is used in casual or non-standard contexts rather than in formal or official usage.
-
C.
usedInSpokenForm
Indicates that something (such as a word, name, or expression) is employed in spoken language or oral communication.
-
D.
usedPrimarilyIn
Indicates that something is mainly or most commonly employed within a particular context, domain, or purpose.
-
E.
usedHyperbolically
Indicates that the action or property is being expressed with deliberate exaggeration for emphasis or effect, rather than as a literal statement.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ca842123588190b3f2e1a69037d141 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd081c2b048190aa6930de3bf2f87f |
completed | April 1, 2026, 11:57 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:34 p.m.