Triple
T28677635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitrospingidae |
E725911
|
entity |
| Predicate | formerPlacement |
P194418
|
FINISHED |
| Object | Thraupidae |
—
|
NE NERFINISHED |
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: Thraupidae | Statement: [Mitrospingidae, formerPlacement, Thraupidae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerPlacement Context triple: [Mitrospingidae, formerPlacement, Thraupidae]
-
A.
previousPlacement
chosen
Indicates that one entity occupied a position, role, or location before another specified placement or assignment.
-
B.
formerSiteOf
Indicates that a location previously hosted or contained something (such as a structure, organization, or event) that is no longer present there.
-
C.
formerGround
Indicates that an entity previously served as the ground or base for another entity but no longer holds that role.
-
D.
placementIn
Indicates that one entity is located or positioned within the spatial or structural bounds of another entity.
-
E.
formerMovement
Indicates that an entity previously belonged to or was associated with a particular movement but is no longer part of it.
- 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_69f01d867608819086bc3e6b4f9de866 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: April 28, 2026, 5:07 a.m.