Triple
T9512550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talokan |
E229435
|
entity |
| Predicate | secrecyStatus |
P13085
|
FINISHED |
| Object | hidden civilization |
—
|
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: hidden civilization | Statement: [Talokan, secrecyStatus, hidden civilization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secrecyStatus Context triple: [Talokan, secrecyStatus, hidden civilization]
-
A.
hasTypeOfSecrecy
chosen
Indicates that something is associated with a particular kind or level of secrecy.
-
B.
keepsSecretAbout
Indicates that one entity intentionally withholds or conceals information regarding another specified entity or topic from others.
-
C.
canBeSecret
Indicates that something has the potential or suitability to be kept hidden or confidential from others.
-
D.
wasInitiallyKeptSecret
Indicates that the referenced information, action, or relationship was originally concealed or not disclosed to others.
-
E.
knowsSecret
Indicates that one entity is aware of confidential or hidden information about another entity or situation.
- 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_69ca84777560819084cddd999badc1aa |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd986aa99c8190b2eaa7f9b111aa2e |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca567ca448190bf4bcce8ce7dd54f |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:58 p.m.