Triple
T20426082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clov |
E501003
|
entity |
| Predicate | cannotWalkProperly |
P140087
|
FINISHED |
| Object | True |
—
|
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: True | Statement: [Clov, cannotWalkProperly, True]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotWalkProperly Context triple: [Clov, cannotWalkProperly, True]
-
A.
couldMoveBipedally
Indicates the ability of an entity to move using two limbs for locomotion, such as walking or running on two legs.
-
B.
dropFeet
Indicates that an entity lowers or places its feet down, typically from a raised or suspended position.
-
C.
hasFootCrossing
Indicates that one entity has a designated crossing point specifically intended for pedestrians on foot.
-
D.
hasWalkingAllowed
Indicates that walking is permitted within or across the referenced area or context.
-
E.
walkOffHitBy
Indicates a game-ending situation where a batter reaches base safely on a hit that results in the immediate conclusion of the contest.
- 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_69e0b4aa68fc8190b1a14c55575ef04a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67ba86ed88190bf2d4448d2abcdc7 |
completed | April 20, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_69e58d766b408190a1d3698145fb6d30 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:30 a.m.