Triple
T7066154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intelligence Support Activity |
E164355
|
entity |
| Predicate | sizeStatus |
P74814
|
FINISHED |
| Object | not publicly disclosed |
—
|
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: not publicly disclosed | Statement: [Intelligence Support Activity, sizeStatus, not publicly disclosed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sizeStatus Context triple: [Intelligence Support Activity, sizeStatus, not publicly disclosed]
-
A.
sizeCategory
Indicates the relative size classification assigned to an entity compared to others (e.g., small, medium, large).
-
B.
sizeDescription
Indicates a relationship where one entity provides descriptive information about the size or scale of another entity.
-
C.
sizeDefinedBy
Indicates that the size or magnitude of one entity is determined, constrained, or specified by another entity.
-
D.
bodySize
Indicates the relative physical magnitude or scale of an entity’s body, such as how large or small it is.
-
E.
sizeIncreasedTo
Indicates that an entity’s size has changed and reached a specified larger value or magnitude.
- F. None of above. chosen
Provenance (4 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_69c688796c148190adb2f1596f595f22 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4a4e7188190aef123ff1a2aa473 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bdc1f08190975fcdbbb1854d1e |
completed | March 27, 2026, 7:59 p.m. |
| PDg | Predicate description generation | batch_69c6e4a15b088190bee9a23e94aaac53 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:39 p.m.