Triple
T17214331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hobbit (1982 video game) |
E417812
|
entity |
| Predicate | hasParserName |
P100874
|
FINISHED |
| Object | Inglish |
—
|
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: Inglish | Statement: [The Hobbit (1982 video game), hasParserName, Inglish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParserName Context triple: [The Hobbit (1982 video game), hasParserName, Inglish]
-
A.
hasComponentName
Indicates that an entity includes or is associated with a component identified by a specific name.
-
B.
hasRootName
Indicates that an entity is associated with a fundamental or original name from which its other names or forms are derived.
-
C.
hasNameString
chosen
Indicates that an entity is associated with a specific textual string used as its name.
-
D.
hasRuleName
Indicates that an entity is associated with a specific rule identified by a particular name.
-
E.
hasFormName
Indicates that an entity is associated with a specific form identified by a particular name.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42dc8d3e88190a89bee6b75392360 |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.