Triple
T5110612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P. L. Travers |
E115204
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Goff |
E211687
|
NE 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: Goff | Statement: [P. L. Travers, familyName, Goff]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Goff Context triple: [P. L. Travers, familyName, Goff]
-
A.
Goff
chosen
Goff is a surname most notably associated with Bruce Goff, an innovative American architect known for his unconventional and organic designs.
-
B.
Griese
Griese is a surname most prominently associated with Bob Griese, the Hall of Fame American football quarterback.
-
C.
Gage
Gage is a surname of English origin borne by various notable individuals, including historical and contemporary figures.
-
D.
Lohse
Lohse is a German surname borne by various notable individuals in fields such as science, sports, and the arts.
-
E.
Fassel
Fassel is a surname most notably associated with Jim Fassel, a former head coach of the New York Giants in the National Football League.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75ad362c8190b9cbded390aaea3c |
completed | March 20, 2026, 4:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bebaa719748190930dceaeedb346c2 |
completed | March 21, 2026, 3:35 p.m. |
Created at: March 20, 2026, 1:41 p.m.