Triple
T23856193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vultur |
E592315
|
entity |
| Predicate | includesVeryLargeBirds |
P73619
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Vultur, includesVeryLargeBirds, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesVeryLargeBirds Context triple: [Vultur, includesVeryLargeBirds, true]
-
A.
hasBirdSpecies
Indicates that there exists a relationship in which a subject possesses, contains, or is associated with a particular bird species.
-
B.
hasLargeSpecies
chosen
Indicates that an entity possesses or includes at least one species that is considered large in size.
-
C.
isLandBird
Indicates that the subject is a bird species that primarily lives on land rather than in aquatic or marine environments.
-
D.
largestBirdOfPreyIn
Indicates that one entity is the largest bird of prey occurring within the geographic area or region specified by the other entity.
-
E.
typicalBird
Indicates that the subject is considered a representative or standard example of a bird, exhibiting the common or characteristic features associated with birds.
- 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c98b29a881909eb60c1be1acdbe9 |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:12 p.m.