Triple
T394218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 99th United States Congress |
E8944
|
entity |
| Predicate | reshaped |
P772
|
FINISHED |
| Object | United States defense organization |
—
|
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: United States defense organization | Statement: [99th United States Congress, reshaped, United States defense organization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reshaped Context triple: [99th United States Congress, reshaped, United States defense organization]
-
A.
shaped
Indicates that one entity has given form, contour, or structure to another entity or outcome.
-
B.
shape
Indicates that one entity has a particular geometric or physical form characterized by the other entity.
-
C.
reorganizedAs
Indicates that an existing entity has been restructured or reconfigured into a new organizational form or arrangement.
-
D.
reorganized
chosen
Indicates that an entity has changed the structure, order, or arrangement of another entity or set of entities from a previous configuration.
-
E.
redesigned
Indicates that an entity has been modified or created anew in terms of its structure, appearance, or functionality, replacing a previous design.
- 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec77a8a08190b6f96373aa8c1346 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96bd3848190a66ca14dfbd26da5 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.