Triple
T27505984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyliidae |
E694278
|
entity |
| Predicate | traditionallyClassifiedWith |
P11158
|
FINISHED |
| Object | warblers |
—
|
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: warblers | Statement: [Hyliidae, traditionallyClassifiedWith, warblers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyClassifiedWith Context triple: [Hyliidae, traditionallyClassifiedWith, warblers]
-
A.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
B.
traditionClassification
Indicates how a given item, practice, or concept is categorized within a particular tradition or system of traditions.
-
C.
classificationOf
Indicates that one entity serves as a classification, category, or type under which another entity is grouped or organized.
-
D.
isClassifiedUnder
Indicates that one entity is categorized or grouped within a broader class, type, or category represented by another entity.
-
E.
traditionallyOneOf
chosen
Indicates that something is customarily or historically considered to belong to a specific set, category, or group.
- 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: April 27, 2026, 1:13 p.m.