Triple
T22345924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarence intelligence network |
E552390
|
entity |
| Predicate | gathered |
P124608
|
FINISHED |
| Object | military intelligence |
—
|
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: military intelligence | Statement: [Clarence intelligence network, gathered, military intelligence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gathered Context triple: [Clarence intelligence network, gathered, military intelligence]
-
A.
gathering
Indicates that one or more entities are coming together or being brought together into a group at a particular time or place.
-
B.
collectedWith
chosen
Indicates that one entity was gathered, acquired, or obtained together with another entity as part of the same collection event or process.
-
C.
held
Indicates that one entity physically grasped, carried, or kept another entity in its possession or control.
-
D.
actedTogetherWith
Indicates that two entities participated in the same performance or production, collaborating or appearing together in an acting context.
-
E.
collectedAs
Indicates that one entity has been gathered, acquired, or assembled as part of another entity, such as a collection, set, or group.
- 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157981c0881909ac74d68b99075c2 |
completed | April 29, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.