Triple
T355454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bob Cousy |
E7532
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Robert |
E2918
|
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: Robert | Statement: [Bob Cousy, givenName, Robert]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Robert Context triple: [Bob Cousy, givenName, Robert]
-
A.
Robert
chosen
Robert is a common masculine given name of Germanic origin, widely used in English-speaking countries.
-
B.
Roy
Roy is a common masculine given name of Celtic origin, often used independently or as a nickname for longer names.
-
C.
Thomas
Thomas is the given name of Confederate General "Stonewall" Jackson, a prominent military leader during the American Civil War.
-
D.
Thomas
Thomas is the given name of Thomas Malthus, the influential English economist and demographer known for his theories on population growth and resource limits.
-
E.
Thomas
Thomas is the full given name of Tom Brady, the legendary NFL quarterback widely regarded as one of the greatest players in American football history.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebad8bf08190b4a38ffd9157d641 |
completed | Feb. 28, 2026, 1:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a50e1f11c08190a0fb6198ca7b61e8 |
completed | March 2, 2026, 4:12 a.m. |
Created at: Feb. 28, 2026, 1:08 p.m.