Triple
T27505781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donacobiidae |
E694273
|
entity |
| Predicate | historicallyPlacedIn |
P193823
|
FINISHED |
| Object | Troglodytidae |
—
|
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: Troglodytidae | Statement: [Donacobiidae, historicallyPlacedIn, Troglodytidae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyPlacedIn Context triple: [Donacobiidae, historicallyPlacedIn, Troglodytidae]
-
A.
historicallyLocatedNear
Indicates that, in a historical context, one entity was geographically situated close to another entity.
-
B.
locatedInHistoricPeriod
Indicates that an entity exists, occurs, or is situated within a specific historic period or era.
-
C.
historicalLocationOf
Indicates that a place served as a significant site or setting for an entity during a particular historical period or event.
-
D.
locatedInHistoricSite
Indicates that an entity is situated within or on the grounds of a place officially recognized as a historic site.
-
E.
historicallyLocatedOutside
Indicates that an entity was historically situated beyond the boundaries or limits of another specified place or region.
- F. None of above. chosen
Provenance (4 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
| PDg | Predicate description generation | batch_69fd57b9cdec81908536c4159e375931 |
completed | May 8, 2026, 3:25 a.m. |
Created at: April 27, 2026, 1:13 p.m.