Triple
T19172815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Croz Spur |
E469366
|
entity |
| Predicate | gearRequired |
P130667
|
FINISHED |
| Object | ice tools |
—
|
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: ice tools | Statement: [Croz Spur, gearRequired, ice tools]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gearRequired Context triple: [Croz Spur, gearRequired, ice tools]
-
A.
crewRequired
Indicates that a certain number or type of crew members is necessary to operate or support the associated entity or activity.
-
B.
gear
Indicates that one entity functions as a gear or toothed mechanical component that transmits motion or force to another entity.
-
C.
hasRunningGear
Indicates that an entity is equipped with or possesses running gear, such as the mechanical components that enable movement or operation.
-
D.
hasArrestingGear
Indicates that an entity is equipped with a system or mechanism used to rapidly decelerate and stop another entity, typically during landing or capture.
-
E.
typicalGear
chosen
Indicates that the object represents the usual or standard equipment or gear commonly associated with the subject.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f16544948190bd10ca7804dd27a5 |
completed | April 20, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.