Triple
T12435743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. National Security Presidential Directive |
E297138
|
entity |
| Predicate | oftenMarkedAs |
P34854
|
FINISHED |
| Object | Top Secret |
—
|
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: Top Secret | Statement: [U.S. National Security Presidential Directive, oftenMarkedAs, Top Secret]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenMarkedAs Context triple: [U.S. National Security Presidential Directive, oftenMarkedAs, Top Secret]
-
A.
usedMark
Indicates that one entity has employed or applied a particular mark, symbol, or indicator in some context or action.
-
B.
commonlyMarkedBy
chosen
Indicates that one entity is typically characterized, identified, or distinguished by the presence of another entity or feature.
-
C.
marked
Indicates that one entity has been identified, labeled, or highlighted in some way by another entity.
-
D.
reportedMarks
Indicates that an entity has formally communicated or submitted the marks/grades of another entity (such as a student or assessment) to a relevant party or system.
-
E.
marksOn
Indicates that one entity bears visible signs, traces, or imprints that have been made or left by 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94df948308190ace333230a4a3b38 |
completed | April 10, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69d94d391c548190996a8c698357f273 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.