Triple
T26839470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fernandomania |
E675737
|
entity |
| Predicate | positionOfMainSubject |
P12364
|
FINISHED |
| Object | pitcher |
—
|
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: pitcher | Statement: [Fernandomania, positionOfMainSubject, pitcher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOfMainSubject Context triple: [Fernandomania, positionOfMainSubject, pitcher]
-
A.
positionOfMainFigure
Indicates the spatial location or placement of the primary or most important figure within a scene or composition.
-
B.
hasSubjectPosition
chosen
Indicates that an entity occupies or is assigned to a particular subject role or position within a structure, context, or organization.
-
C.
subjectPosition
Indicates the spatial or logical position of a subject relative to a reference frame, context, or other entities.
-
D.
subjectPositionDescribed
Indicates that the subject’s spatial or situational position is explicitly described or specified in relation to some reference frame or context.
-
E.
positionMentioned
Indicates that a specific position, role, or location is explicitly referenced or mentioned in relation to an entity or event.
- 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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 27, 2026, 5:07 a.m.