Triple
T31991240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stool 60 |
E816874
|
entity |
| Predicate | legConfiguration |
P70462
|
FINISHED |
| Object | three-legged |
—
|
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: three-legged | Statement: [Stool 60, legConfiguration, three-legged]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legConfiguration Context triple: [Stool 60, legConfiguration, three-legged]
-
A.
legs
chosen
Indicates that an entity possesses legs, specifying the presence or number of leg-like appendages associated with it.
-
B.
legOrder
Indicates the sequential position or ordering of a specific leg within a multi-leg structure, process, or route.
-
C.
legOrientation
Indicates the relative positioning or directional alignment of an entity’s leg(s) with respect to a reference frame or another object.
-
D.
hasLegType
Indicates that an entity possesses a specific type or category of legs.
-
E.
legCharacteristic
Indicates a characteristic, property, or attribute that specifically pertains to the legs of an entity.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b3b9ad2c8190ba59409cbd3da87f |
completed | May 3, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:13 a.m.