Triple
T173533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Hancock |
E3527
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Hancock |
E3527
|
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: Hancock | Statement: [John Hancock, familyName, Hancock]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hancock Context triple: [John Hancock, familyName, Hancock]
-
A.
Hancock
chosen
Hancock is a prominent surname most famously associated with John Hancock, a key figure of the American Revolution and first signer of the United States Declaration of Independence.
-
B.
Coming Home
"Coming Home" is a song featured on the album "Once Again," likely recognized as one of its individual tracks.
-
C.
Mr. Secretary
"Mr. Secretary" is the traditional formal style of address used for the United States Secretary of the Treasury.
-
D.
Mr. Secretary
Mr. Secretary is the formal style of address traditionally used for the United States Secretary of Defense.
-
E.
Mr. Secretary
"Mr. Secretary" is the formal style of address traditionally used for the United States Secretary of Transportation.
- 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a258e1ec008190a89dd452f72574f4 |
completed | Feb. 28, 2026, 2:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a2eb7a519c81909922f45628f43c69 |
completed | Feb. 28, 2026, 1:19 p.m. |
Created at: Feb. 28, 2026, 2:39 a.m.