Triple
T35806695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old School |
E1035118
|
entity |
| Predicate | setupRequirement |
P184133
|
FINISHED |
| Object | opponent standing near the corner |
—
|
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: opponent standing near the corner | Statement: [Old School, setupRequirement, opponent standing near the corner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setupRequirement Context triple: [Old School, setupRequirement, opponent standing near the corner]
-
A.
establishedRequirement
Indicates that one entity has formally set or defined a requirement that another entity is expected to satisfy or comply with.
-
B.
maintenanceRequirement
Indicates that an entity is obligated to perform, schedule, or adhere to specific maintenance activities or conditions for another entity or system.
-
C.
componentRequirement
Indicates that one component depends on or necessitates the presence or use of another component to function or be considered complete.
-
D.
fallbackRequirement
Indicates a secondary or backup condition that applies when the primary requirement cannot be met.
-
E.
projectRequirement
Indicates that one entity specifies a necessary condition, resource, or criterion that must be satisfied for a project associated with another entity.
- F. None of above. chosen
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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:06 p.m.