Triple
T10105805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | dusky scrubfowl |
E216316
|
entity |
| Predicate | belongsToEcologicalGroup |
P34930
|
FINISHED |
| Object | ground-nesting birds |
—
|
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: ground-nesting birds | Statement: [dusky scrubfowl, belongsToEcologicalGroup, ground-nesting birds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToEcologicalGroup Context triple: [dusky scrubfowl, belongsToEcologicalGroup, ground-nesting birds]
-
A.
belongsToSpecies
Indicates that an individual organism is a member of, or classified under, a particular biological species.
-
B.
taxonGroup
Indicates a classification relationship where one taxon is grouped within or associated with a broader taxonomic group.
-
C.
hasFaunaGroup
Indicates that an entity possesses, contains, or is associated with a particular group or assemblage of animal life.
-
D.
containsEcologicalTypes
chosen
Indicates that one entity includes or encompasses specific ecological types or categories within it.
-
E.
hasEcology
Indicates that an entity has a particular ecological context, such as its habitat, environmental role, or interactions within an ecosystem.
- 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_69ca83d039f08190b9d10363221c69fb |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd09dde888190bb550a3cd0b204fe |
completed | April 2, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:03 p.m.