Triple
T5260676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arba Olamot |
E118814
|
entity |
| Predicate | conceptualLevel |
P11425
|
FINISHED |
| Object | metaphysical |
—
|
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: metaphysical | Statement: [Arba Olamot, conceptualLevel, metaphysical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conceptualLevel Context triple: [Arba Olamot, conceptualLevel, metaphysical]
-
A.
classificationLevel
Indicates the degree or tier within an ordered system or hierarchy to which something is assigned for categorization or control purposes.
-
B.
conceptualRole
Indicates the functional or semantic role that one concept plays in relation to another within a conceptual structure or system.
-
C.
logicalLevel
chosen
Indicates the relative position or depth of something within a hierarchy of abstraction, reasoning, or logical structure.
-
D.
operationalConcept
Indicates that one entity defines, specifies, or embodies the operational concept or way of functioning for another entity.
-
E.
hasConceptualOrigin
Indicates that something conceptually originates from, is derived from, or is fundamentally based on another thing.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bcf026c8190881b6e14b962a3c9 |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.