Triple
T35746362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sadan Cave |
E1033192
|
entity |
| Predicate | exitOrientation |
P88382
|
FINISHED |
| Object | open plain with rice fields |
—
|
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: open plain with rice fields | Statement: [Sadan Cave, exitOrientation, open plain with rice fields]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exitOrientation Context triple: [Sadan Cave, exitOrientation, open plain with rice fields]
-
A.
exitTo
chosen
Indicates that one location or entity serves as a passage or route leading directly to another location or entity.
-
B.
accessibleExit
Indicates that an exit is designed and configured to be usable by people with disabilities, meeting accessibility requirements.
-
C.
exitRoutes
Indicates that there are designated paths or ways for entities to leave or move out from a particular place or situation.
-
D.
escapeStatus
Indicates whether an entity has escaped, is in the process of escaping, or has not escaped from a given situation or confinement.
-
E.
escapeOutcome
Indicates the result or consequence of an attempt to escape, such as whether it succeeded, failed, or led to a particular follow-up state.
- 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_69f76e119d508190a3873cb302063832 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a193bec481909a83b202d36d5e3d |
completed | May 3, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.