Triple
T1584504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aves |
E34033
|
entity |
| Predicate | hasCovering |
P10512
|
FINISHED |
| Object | feathers |
—
|
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: feathers | Statement: [Aves, hasCovering, feathers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCovering Context triple: [Aves, hasCovering, feathers]
-
A.
hasCoverType
chosen
Indicates that one entity possesses or is associated with a specific type or category of cover.
-
B.
hasCoverage
Indicates that one entity provides insurance or protection coverage for another entity or subject.
-
C.
isCoveredBy
Indicates that one entity is physically or conceptually overlaid, protected, or enclosed by another entity.
-
D.
hasCoveringGroup
Indicates that one group serves as a covering group (typically a covering or universal covering in the group-theoretic sense) for another group.
-
E.
hasCoverName
Indicates that one entity uses or is known by an alternative, often secret or assumed, name in relation to another entity or context.
- 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_69a885fceb2c8190b47e0f7c0aefbff0 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abacfb1144819080c5687175aba1e1 |
completed | March 7, 2026, 4:43 a.m. |
| PD | Predicate disambiguation | batch_69aa61b0f5bc8190b1dc272990a59c13 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:27 p.m.