Triple
T26709625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alcippe |
E673376
|
entity |
| Predicate | traditionalPlacement |
P37794
|
FINISHED |
| Object | Old World babblers |
E1738141
|
NE 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: Old World babblers | Statement: [Alcippe, traditionalPlacement, Old World babblers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalPlacement Context triple: [Alcippe, traditionalPlacement, Old World babblers]
-
A.
canonicalPlacement
Indicates the standard or preferred position or arrangement of one entity relative to another within a defined structure or system.
-
B.
traditionalPlacementInCorpus
Indicates the conventional or historically established position of a work or text within a larger corpus or collection.
-
C.
traditionalOrder
Indicates that entities are arranged or occur according to a customary, historically established sequence or hierarchy.
-
D.
traditionalPositions
chosen
Indicates that one entity holds or is associated with customary or historically established roles, stances, or arrangements in relation to another entity.
-
E.
traditionalRule
Indicates that an entity follows, embodies, or is governed by a customary or long-established rule or norm.
- F. None of above.
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_69eecda3a22881908f3061c760b9d542 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a12093a8c808190bfb87dff7a5c4da2 |
completed | May 23, 2026, 8:08 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 27, 2026, 3:35 a.m.