Triple
T27370033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Passerimorphae |
E690286
|
entity |
| Predicate | hasDefiningTrait |
P128540
|
FINISHED |
| Object | anisodactyl foot common among passerines |
—
|
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: anisodactyl foot common among passerines | Statement: [Passerimorphae, hasDefiningTrait, anisodactyl foot common among passerines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDefiningTrait Context triple: [Passerimorphae, hasDefiningTrait, anisodactyl foot common among passerines]
-
A.
associatedWithDefiningTrait
Indicates that one entity is linked to another as a key characteristic or defining feature of it.
-
B.
containsTrait
chosen
Indicates that one entity possesses, exhibits, or is characterized by a specified trait.
-
C.
hasDefinition
Indicates that one entity provides the meaning, explanation, or definition of another entity.
-
D.
hasCommonTraitWith
Indicates that two entities share at least one trait, characteristic, or property in common.
-
E.
containsTraitStack
Indicates that one entity possesses or includes a specific collection (stack) of traits associated with another 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_69ef51ff826081909e42c8e2bfb97941 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 27, 2026, 12:18 p.m.