Triple
T2290909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falconiformes |
E51498
|
entity |
| Predicate | modernCircumscription |
P36225
|
FINISHED |
| Object | falcons and caracaras only |
—
|
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: falcons and caracaras only | Statement: [Falconiformes, modernCircumscription, falcons and caracaras only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernCircumscription Context triple: [Falconiformes, modernCircumscription, falcons and caracaras only]
-
A.
modernUse
Indicates how something is currently used or applied in modern times.
-
B.
modernPractice
Indicates that an entity engages in or reflects a contemporary, up-to-date way of doing something, following current methods, standards, or trends.
-
C.
modernizedFor
Indicates that something has been updated, adapted, or improved to suit more recent standards, technologies, or conditions.
-
D.
modernState
Indicates that an entity functions as a contemporary, currently existing state or nation in the modern era.
-
E.
logicSystem
Indicates a relationship where an entity is associated with, defined within, or governed by a particular logical framework or system of formal reasoning.
- 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_69a88b09c644819090b503456d96bf70 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc27536588190a74731b5537c90ee |
completed | March 7, 2026, 6:15 a.m. |
| PD | Predicate disambiguation | batch_69abbdbc8bcc8190a183481d766965a4 |
completed | March 7, 2026, 5:55 a.m. |
| PDg | Predicate description generation | batch_69abbe1ecb7081909c2c66da08a48ab7 |
completed | March 7, 2026, 5:56 a.m. |
Created at: March 4, 2026, 7:48 p.m.