Triple
T9783668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Horse Show |
E237438
|
entity |
| Predicate | hasCircuitRole |
P90632
|
FINISHED |
| Object | culminating indoor show of U.S. fall circuit |
—
|
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: culminating indoor show of U.S. fall circuit | Statement: [National Horse Show, hasCircuitRole, culminating indoor show of U.S. fall circuit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCircuitRole Context triple: [National Horse Show, hasCircuitRole, culminating indoor show of U.S. fall circuit]
-
A.
hasLegalRole
Indicates that an entity holds a specific legal capacity, status, or function in relation to another entity or context.
-
B.
hasStageRole
Indicates that an entity performs or holds a specific role or character in a staged performance or theatrical production.
-
C.
hasRoleInNetwork
Indicates that an entity holds a specific functional position or responsibility within a particular network.
-
D.
hasAuxiliaryRole
Indicates that an entity serves in a supporting or secondary capacity to another entity or primary role.
-
E.
hasContactRole
Indicates that an entity serves in a specific role or capacity as a contact for 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_69ca84da927881909bda80caecad6010 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda1b7740c8190bfb4997eb683d78a |
completed | April 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69cd03d77c6c81909b675955bf113320 |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06aa8bc88190904be19c8953def8 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:27 p.m.