Triple
T27639973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operating Thetan |
E696562
|
entity |
| Predicate | highestPubliclyKnownLevel |
P80904
|
FINISHED |
| Object | OT VIII |
—
|
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: OT VIII | Statement: [Operating Thetan, highestPubliclyKnownLevel, OT VIII]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestPubliclyKnownLevel Context triple: [Operating Thetan, highestPubliclyKnownLevel, OT VIII]
-
A.
highestPublishedTierOf
chosen
Indicates the most advanced or top-level tier that has been officially published for a given entity.
-
B.
highestCrestLevel
Indicates the relationship where a given crest or wave has the greatest height level compared to all other relevant crests in the context.
-
C.
formerHighest
Indicates that an entity once held the highest rank, position, or status in a given context but no longer does.
-
D.
typicalHighestLevel
Indicates the usual or most common maximum level or degree that something typically reaches within a given context.
-
E.
hasHighest
Indicates that one entity possesses the greatest value, rank, or level in a specified attribute or set compared to all others.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 2:25 p.m.