Triple
T12009189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Culper Ring |
E285861
|
entity |
| Predicate | maintainedSecrecyUntil |
P94707
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Culper Ring, maintainedSecrecyUntil, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainedSecrecyUntil Context triple: [Culper Ring, maintainedSecrecyUntil, 19th century]
-
A.
wasInitiallyKeptSecret
Indicates that the referenced information, action, or relationship was originally concealed or not disclosed to others.
-
B.
keepsSecretAbout
Indicates that one entity intentionally withholds or conceals information regarding another specified entity or topic from others.
-
C.
confidentialityStatusAtTheTime
chosen
Indicates the level or state of confidentiality that applied to something at a specific point in time.
-
D.
revealedAfter
Indicates that one piece of information, event, or state becomes known or disclosed only subsequent to another specified point in time or condition.
-
E.
revealedBefore
Indicates that one entity becomes known, disclosed, or made apparent earlier in time than another 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903d61a4c81909e6cb6500b61df94 |
completed | April 10, 2026, 2:06 p.m. |
| PD | Predicate disambiguation | batch_69d902b245cc8190af96a9c2bd9c6250 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.