Triple
T11150906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Cup |
E263779
|
entity |
| Predicate | equipmentStandards |
P43031
|
FINISHED |
| Object | FIG-approved apparatus |
—
|
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: FIG-approved apparatus | Statement: [American Cup, equipmentStandards, FIG-approved apparatus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equipmentStandards Context triple: [American Cup, equipmentStandards, FIG-approved apparatus]
-
A.
equipmentProvider
Indicates that one entity supplies or makes available equipment for use by another entity.
-
B.
compatibleStand
Indicates that one entity can be properly supported or held by another entity’s stand or mounting system.
-
C.
hardwareUsed
Indicates that a particular piece of hardware is utilized or employed in performing an action, process, or function involving another entity.
-
D.
unitRequirement
Indicates that one entity specifies a required quantity or unit that another entity must meet or conform to.
-
E.
standardsType
chosen
Indicates the classification or category of standards that apply to or are associated with an entity or activity.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8719e74819095413abc6c79296c |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75ce71944819089eee9b5c9283cbd |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:28 p.m.