Triple
T28001973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort/Da game |
E707170
|
entity |
| Predicate | nameComponentFortMeaning |
P163614
|
FINISHED |
| Object | gone |
—
|
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: gone | Statement: [Fort/Da game, nameComponentFortMeaning, gone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameComponentFortMeaning Context triple: [Fort/Da game, nameComponentFortMeaning, gone]
-
A.
birthNameMeaning
Indicates the semantic meaning or significance associated with a person's birth name.
-
B.
currentNameMeaning
Indicates that the predicate expresses the meaning or significance of an entity’s current name.
-
C.
nameMeaningCertainty
Indicates how certain or confident a source is about the correctness or validity of an entity’s name meaning.
-
D.
ordinalMeaningOfName
Indicates that a name refers to an entity’s position or rank in an ordered sequence (e.g., first, second, third).
-
E.
codeNameMeaning
Indicates that one entity is the meaning, interpretation, or significance associated with another entity’s code name.
- F. None of above. chosen
Provenance (4 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63bd2dc3c81908ee2471fa32c7841 |
completed | May 2, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 7:57 p.m.