Triple
T13855335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple Grandin |
E333048
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Temple |
E436164
|
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: Temple | Statement: [Temple Grandin, givenName, Temple]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Temple Context triple: [Temple Grandin, givenName, Temple]
-
A.
Temple
Temple is a historic legal district in central London, renowned for housing the Inns of Court and many barristers’ chambers.
-
B.
Temple
Temple is the athletic program of Temple University, best known for its NCAA Division I sports teams, particularly in basketball and football.
-
C.
Temple
Temple is a song featured on the soundtrack of the rhythm game Mechanical Bull.
-
D.
Temple
chosen
Temple is a surname of English origin borne by various notable individuals across fields such as politics, sports, and the arts.
-
E.
Temple
"Temple" is a British television drama series produced by Liza Marshall, centered on an underground clinic beneath London where a surgeon treats criminals and desperate patients.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02db9c9c81909bb2d2fbfb7394b1 |
completed | April 14, 2026, 9:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7c0fb7c3c819081fc6f89aa17d6af |
completed | May 3, 2026, 9:41 p.m. |
Created at: April 9, 2026, 10:14 p.m.