Triple
T2290870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falconiformes |
E51498
|
entity |
| Predicate | traditionalClass |
P22943
|
FINISHED |
| Object | Aves |
—
|
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: Aves | Statement: [Falconiformes, traditionalClass, Aves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalClass Context triple: [Falconiformes, traditionalClass, Aves]
-
A.
traditionalCode
Indicates that something adheres to or is characterized by long-established, customary, or historically rooted practices, methods, or norms.
-
B.
traditionalInstitution
Indicates that an entity is a long-established, customary organization or system that embodies and maintains traditional practices or norms.
-
C.
traditionalSocialClass
chosen
Indicates that an entity belongs to or is associated with a particular traditional social class within a social hierarchy.
-
D.
traditionalFunction
Indicates that an entity serves a customary or historically established role or purpose within a cultural or social context.
-
E.
traditionalEnd
Indicates that one entity is the customary or historically established conclusion, outcome, or final stage of another entity or process.
- 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_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. |
Created at: March 4, 2026, 7:48 p.m.