Triple
T321319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archaea |
E6420
|
entity |
| Predicate | archaellaStructure |
P11982
|
FINISHED |
| Object | distinct from bacterial flagella |
—
|
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: distinct from bacterial flagella | Statement: [Archaea, archaellaStructure, distinct from bacterial flagella]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archaellaStructure Context triple: [Archaea, archaellaStructure, distinct from bacterial flagella]
-
A.
architecturalConcept
Indicates that one entity represents or embodies an architectural concept in relation to another entity.
-
B.
survivingStructure
Indicates that a structure continues to exist or remain intact after a potentially destructive event or over a significant period of time.
-
C.
architecturalWork
Indicates that one entity is an architectural creation (such as a building or structure) designed or realized by another entity.
-
D.
architectureType
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
E.
hasArchitecturalFeature
Indicates that one entity possesses, includes, or is characterized by a specific architectural feature or element.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea81a1e88190b3496070eb3d85f5 |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e948048c819098ba4de9261ef2ef |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea08878c8190a5e8a90f620a3888 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.