Triple
T7159130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Intelligence Estimates |
E166892
|
entity |
| Predicate | mayHaveVersion |
P31922
|
FINISHED |
| Object | declassified NIE |
—
|
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: declassified NIE | Statement: [National Intelligence Estimates, mayHaveVersion, declassified NIE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayHaveVersion Context triple: [National Intelligence Estimates, mayHaveVersion, declassified NIE]
-
A.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
B.
hasMultipleVersions
Indicates that an entity exists in more than one distinct version or revision.
-
C.
laterVersion
Indicates that one entity is a subsequent or more recent version of another entity in a version sequence.
-
D.
alsoAvailableInVersion
Indicates that the same item, feature, or content is offered in another specified version or edition.
-
E.
versionOf
chosen
Indicates that one entity is a specific form, edition, or variant derived from or corresponding to 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_69c68887a5cc8190bec0ea96227164f7 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e811d6b081909dafeee1d820c74f |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1cd5c948190a9113b23f7308c21 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:47 p.m.