Triple
T36193310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FEI Eventing |
E1047047
|
entity |
| Predicate | jumpingFeature |
P173291
|
FINISHED |
| Object | knockable fences |
—
|
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: knockable fences | Statement: [FEI Eventing, jumpingFeature, knockable fences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jumpingFeature Context triple: [FEI Eventing, jumpingFeature, knockable fences]
-
A.
showJumpingFeature
chosen
Indicates that an entity displays or performs a jumping-related capability or behavior.
-
B.
jumpHill
Indicates that an entity performs a jumping action over or onto a hill.
-
C.
homeJumperFeature
Indicates a feature that enables or supports jumping directly to a home or main location within a system or interface.
-
D.
BASEJumpingStatus
Indicates whether an entity is currently engaged in, has completed, or is otherwise associated with BASE jumping activities.
-
E.
jumpOff
Indicates an action where an entity propels itself away from or downward from a surface, object, or location.
- 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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.