Triple
T19882332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diaspar |
E477806
|
entity |
| Predicate | entryExitCondition |
P136925
|
FINISHED |
| Object | no known exits for most citizens |
—
|
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: no known exits for most citizens | Statement: [Diaspar, entryExitCondition, no known exits for most citizens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entryExitCondition Context triple: [Diaspar, entryExitCondition, no known exits for most citizens]
-
A.
entryCondition
Indicates the prerequisite state, criteria, or circumstances that must be satisfied before entering or initiating a particular process, state, or context.
-
B.
hasExitFor
Indicates that something provides or includes a specific exit intended for a particular destination, purpose, or user.
-
C.
conditionForLeaving
chosen
Indicates the specific circumstance or requirement under which an entity is permitted or expected to leave a situation, place, or state.
-
D.
terminalCondition
Indicates the condition or set of conditions under which a process, interaction, or state is considered complete and should terminate.
-
E.
exitTo
Indicates that one location or entity serves as a passage or route leading directly to another location or 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658e0ccc88190b6f093035cd6f2a1 |
completed | April 20, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.