Triple
T72351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galliformes |
E1448
|
entity |
| Predicate | locomotion |
P3596
|
FINISHED |
| Object | strong runners |
—
|
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: strong runners | Statement: [Galliformes, locomotion, strong runners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locomotion Context triple: [Galliformes, locomotion, strong runners]
-
A.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
-
B.
displacement
Indicates a change in an entity’s position from one location to another, typically specifying both direction and magnitude of that movement.
-
C.
propulsion
Indicates a relationship where one entity provides the driving force or thrust that moves another entity forward or keeps it in motion.
-
D.
transportation
Indicates the movement of someone or something from one place to another, typically using a vehicle or transit system.
-
E.
terminus
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
- 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_69a24c06b3bc8190aa4ac89026115efc |
completed | Feb. 28, 2026, 1:59 a.m. |
| NER | Named-entity recognition | batch_69a24f6997c081908b202f937eb2b14f |
completed | Feb. 28, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69a24eab7f408190a8275cb82474f575 |
completed | Feb. 28, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69a24f65170c8190bc541c8351456a4d |
completed | Feb. 28, 2026, 2:13 a.m. |
Created at: Feb. 28, 2026, 2:03 a.m.