Triple
T4165837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZF |
E84442
|
entity |
| Predicate | hasAxiomSchema |
P54444
|
FINISHED |
| Object | separation |
—
|
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: separation | Statement: [ZF, hasAxiomSchema, separation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAxiomSchema Context triple: [ZF, hasAxiomSchema, separation]
-
A.
hasAxiom
Indicates that an entity is associated with, defined by, or governed through a specific axiom or set of axioms.
-
B.
hasSchemaLanguage
Indicates that an entity uses, conforms to, or is defined in a particular schema language.
-
C.
foundationAxiomHoldsIn
Indicates that the foundation (or regularity) axiom is satisfied within a given model, structure, or context.
-
D.
hasTypeSystem
Indicates that an entity employs, is governed by, or is associated with a particular type system (a defined set of rules for classifying and constraining types).
-
E.
isModelOf
Indicates that one entity serves as a representation or abstraction that captures the structure or behavior of another entity.
- 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_69aed932cab48190b80ffe35f7029ae1 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af02ac8e788190a8f3563a2903bbad |
completed | March 9, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69af018fb0948190a9701b2e8e5d9bac |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af01ee94ec8190aa6dde54d4571c04 |
completed | March 9, 2026, 5:22 p.m. |
Created at: March 9, 2026, 3:44 p.m.