Triple
T35605093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Ainley |
E1028863
|
entity |
| Predicate | hasWorkedInRegion |
P190281
|
FINISHED |
| Object | Antarctica |
—
|
NE NERFINISHED |
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: Antarctica | Statement: [David Ainley, hasWorkedInRegion, Antarctica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkedInRegion Context triple: [David Ainley, hasWorkedInRegion, Antarctica]
-
A.
hasWorkedIn
Indicates that a person has been employed or has performed work within a particular organization, location, or domain for some period of time.
-
B.
workedInLocation
chosen
Indicates that an entity performed work or held a job in a specified geographic location or place.
-
C.
hasWorkedFor
Indicates that an entity has been employed by or has provided work or services to another entity.
-
D.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
E.
hasWorksLocatedIn
Indicates that the works or creations associated with an entity are situated or stored in a specified location.
- 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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe86cad5108190b0164b8bc6fc23ea |
completed | May 9, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69fe83c0c9888190b6fc40c7f727b569 |
completed | May 9, 2026, 12:45 a.m. |
Created at: May 3, 2026, 4:05 p.m.