Triple
T31648230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Reorganization Act of 1903 |
E807640
|
entity |
| Predicate | affectedComponent |
P179255
|
FINISHED |
| Object | Regular Army |
—
|
NE NERFINISHED |
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: Regular Army | Statement: [Army Reorganization Act of 1903, affectedComponent, Regular Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectedComponent Context triple: [Army Reorganization Act of 1903, affectedComponent, Regular Army]
-
A.
affectedEntity
Indicates that an entity is the one that is impacted, influenced, or acted upon as a result of an event, action, or process.
-
B.
affectedClass
Indicates that one entity (typically a change, event, or issue) has an impact on or is relevant to a particular class or category of items.
-
C.
affectedProject
Indicates that one entity has an impact on, or is influenced by, a particular project.
-
D.
affectedAsset
Indicates that an entity has an impact on, or causes a change to, a particular asset.
-
E.
affectedProvision
Indicates that a particular legal provision is impacted, modified, or influenced by another action, decision, or provision.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7201e241c819092d56a7bb99dc94d |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: April 30, 2026, 10:52 p.m.