Triple
T16917005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asia Minor Agreement |
E410345
|
entity |
| Predicate | wasSecretUntil |
P60605
|
FINISHED |
| Object | 1917 |
—
|
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: 1917 | Statement: [Asia Minor Agreement, wasSecretUntil, 1917]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasSecretUntil Context triple: [Asia Minor Agreement, wasSecretUntil, 1917]
-
A.
wasInitiallyKeptSecret
chosen
Indicates that the referenced information, action, or relationship was originally concealed or not disclosed to others.
-
B.
secretedBy
Indicates that a substance or product is released or produced by a particular cell, tissue, organ, or organism.
-
C.
revealedSecretOf
Indicates that one entity has disclosed or exposed confidential or previously unknown information belonging to another entity.
-
D.
revealedBefore
Indicates that one entity becomes known, disclosed, or made apparent earlier in time than another entity.
-
E.
revealedAfter
Indicates that one piece of information, event, or state becomes known or disclosed only subsequent to another specified point in time or condition.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cdeb74c08190b6f247cdf4b21405 |
completed | April 18, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.