Triple
T22934952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indochina dry forests |
E569554
|
entity |
| Predicate | hasCharacteristicBird |
P29974
|
FINISHED |
| Object | green peafowl |
—
|
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: green peafowl | Statement: [Indochina dry forests, hasCharacteristicBird, green peafowl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCharacteristicBird Context triple: [Indochina dry forests, hasCharacteristicBird, green peafowl]
-
A.
hasBirdSpecies
chosen
Indicates that there exists a relationship in which a subject possesses, contains, or is associated with a particular bird species.
-
B.
hasBeak
Indicates that an entity possesses a beak as a physical anatomical feature.
-
C.
isBirdLike
Indicates that one entity resembles or shares key characteristics or behaviors with birds.
-
D.
typicalBird
Indicates that the subject is considered a representative or standard example of a bird, exhibiting the common or characteristic features associated with birds.
-
E.
hasFeatheredMembers
Indicates that at least some members of a group or category possess feathers.
- 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_69e24590862c8190858f180ad302adab |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181350c7881908a72dc7a30e1aaff |
completed | April 29, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:44 p.m.