Triple
T20778770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K.E.W. |
E511422
|
entity |
| Predicate | isLevelOf |
P2393
|
FINISHED |
| Object | O.T.O. initiation |
—
|
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: O.T.O. initiation | Statement: [K.E.W., isLevelOf, O.T.O. initiation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLevelOf Context triple: [K.E.W., isLevelOf, O.T.O. initiation]
-
A.
hasLevel
chosen
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
-
B.
definesLevel
Indicates that one entity specifies or establishes the degree, stage, or intensity at which another entity is set or operates.
-
C.
exportLevel
Indicates the degree or extent to which something is produced in one place and sent out or made available to other places or markets.
-
D.
containsLevel
Indicates that one entity includes or encompasses a specific level or layer within its structure or hierarchy.
-
E.
recognizesLevel
Indicates that one entity acknowledges, identifies, or is aware of the degree, rank, or intensity associated with another entity.
- 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_69e0b4cac7a48190a715cb3d545df2b4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c26ed1a08190bb73824672328d98 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:37 p.m.