Triple
T30169381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larak |
E766875
|
entity |
| Predicate | hasNoSecureExcavation |
P201803
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Larak, hasNoSecureExcavation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoSecureExcavation Context triple: [Larak, hasNoSecureExcavation, true]
-
A.
hasExcavationNumber
Indicates that an entity is associated with a specific excavation identifier assigned during an archaeological or similar dig.
-
B.
hasInsecurity
Indicates that one entity experiences feelings of doubt, vulnerability, or lack of confidence related to another entity or aspect.
-
C.
hasSecretExit
Indicates that something includes or is connected to a hidden or concealed way out.
-
D.
canSecure
Indicates that one entity has the ability or capacity to protect, safeguard, or make another entity safe from harm, loss, or unauthorized access.
-
E.
hasFalseDoor
Indicates that an entity possesses or includes a false door, typically an architectural or symbolic doorway that does not function as a real entrance.
- F. None of above. chosen
Provenance (4 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00233e2170819084bee0c8f74cc1a4 |
completed | May 10, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_6a0022943fd08190b73007f080d5971d |
completed | May 10, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_6a00233d32bc8190bea60b09b46ee7bc |
completed | May 10, 2026, 6:18 a.m. |
Created at: April 29, 2026, 7:24 p.m.