Triple
T16613410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melophorus |
E403632
|
entity |
| Predicate | workerTrait |
P123551
|
FINISHED |
| Object | high running speed |
—
|
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: high running speed | Statement: [Melophorus, workerTrait, high running speed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workerTrait Context triple: [Melophorus, workerTrait, high running speed]
-
A.
workerCaste
Indicates a relationship where an entity belongs to or is classified within a particular worker caste or labor-based social group.
-
B.
workDistributor
Indicates that one entity is responsible for assigning, allocating, or distributing work or tasks to others.
-
C.
workerPolymorphism
Indicates that an entity functions as a worker in multiple forms or roles, varying its behavior or type depending on context.
-
D.
workAttribute
Indicates that a particular characteristic, quality, or property is associated with a specific work or piece of work.
-
E.
notableWorker
Indicates that the subject is a worker who is distinguished or recognized for being particularly important, prominent, or exemplary in their work.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e360983d2c8190b1fe7f18aedfbde1 |
completed | April 18, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7fb02f481908885a226c2191231 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:17 a.m.