Triple
T6003890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Yanks |
E133660
|
entity |
| Predicate | demonstratesTypeOf |
P67300
|
FINISHED |
| Object | sports team nickname |
—
|
LITERAL 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: sports team nickname | Statement: [The Yanks, demonstratesTypeOf, sports team nickname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demonstratesTypeOf Context triple: [The Yanks, demonstratesTypeOf, sports team nickname]
-
A.
hasTypeOfDemonstration
Indicates that an event or action is characterized by a specific kind or category of demonstration.
-
B.
demonstratedBy
Indicates that something is shown, proven, or made evident through the actions, behavior, or example of a particular entity.
-
C.
demonstratedOn
Indicates that an action, behavior, or property is shown, illustrated, or proven using a particular entity as the example or subject.
-
D.
exampleType
chosen
Indicates that one entity serves as a representative or illustrative instance of the type or category defined by another entity.
-
E.
designedToDemonstrate
Indicates that something was intentionally created or arranged for the purpose of showing, illustrating, or proving a particular concept, feature, or behavior.
- 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f0f63148190826198281dce3713 |
completed | March 22, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c049e3316c819087ea635fa7ee8472 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.