Triple
T30431346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cortlandt Skinner |
E774174
|
entity |
| Predicate | notableUnitNickname |
P6622
|
FINISHED |
| Object | Skinner’s Greens |
E772955
|
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: Skinner’s Greens | Statement: [Cortlandt Skinner, notableUnitNickname, Skinner’s Greens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableUnitNickname Context triple: [Cortlandt Skinner, notableUnitNickname, Skinner’s Greens]
-
A.
notableTeamNickname
chosen
Indicates that a team is commonly known by a particular nickname that is notable or widely recognized.
-
B.
notableCommanderNickname
Indicates that a notable military commander is commonly known by a particular nickname.
-
C.
nicknamedByAllies
Indicates that an entity is referred to by a particular nickname specifically given or used by its allies.
-
D.
notableNickname
Indicates that one entity is a well-known or widely recognized nickname or moniker for another entity.
-
E.
notableMilitaryUnit
Indicates that an entity is a military unit that holds particular significance, prominence, or recognition in some context.
- F. None of above.
Provenance (4 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_69f22492d2a88190995ce8745d9becaa |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2798ba2cd48190b7d61c30747e94d7 |
completed | June 9, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:07 p.m.