Triple
T38099938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hudson |
E951348
|
entity |
| Predicate | formerLeaderOf |
P18663
|
FINISHED |
| Object | Manhattan Clan |
—
|
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: Manhattan Clan | Statement: [Hudson, formerLeaderOf, Manhattan Clan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerLeaderOf Context triple: [Hudson, formerLeaderOf, Manhattan Clan]
-
A.
hadPrincipalLeader
Indicates that an entity was led or headed by a primary or chief leader.
-
B.
notableFormerLeader
chosen
Indicates that the subject was once a leader of the object and is recognized as particularly significant or prominent in that former leadership role.
-
C.
currentDeFactoLeader
Indicates that the specified person is the individual who effectively holds and exercises the highest leadership authority over the given entity at the present time, regardless of formal or legal title.
-
D.
formerPresidentOf
Indicates that one entity previously held, but no longer holds, the official position of president of another entity.
-
E.
predecessorInOffice
Indicates that one officeholder directly held a particular position before another officeholder in an official succession.
- 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0136e4af808190b529d324bbf0c5d9 |
completed | May 11, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_6a01369141c4819091cb8064913a44ca |
completed | May 11, 2026, 1:53 a.m. |
Created at: May 3, 2026, 4:21 p.m.