Triple
T803247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States National Guard |
E17173
|
entity |
| Predicate | establishedAsModernForce |
P15394
|
FINISHED |
| Object | 1903 |
—
|
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: 1903 | Statement: [United States National Guard, establishedAsModernForce, 1903]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsModernForce Context triple: [United States National Guard, establishedAsModernForce, 1903]
-
A.
hasMilitarySignificanceSince
chosen
Indicates that something has held military importance or strategic value starting from a specified point in time.
-
B.
modernizedBy
Indicates that an entity has been updated, improved, or brought up to modern standards through the actions or influence of another entity.
-
C.
hasModernInstitution
Indicates that an entity possesses, hosts, or is associated with a contemporary institution or organization.
-
D.
militaryOrganization
Indicates that an entity functions as, or is associated with, a structured armed forces or defense-related organization.
-
E.
numberInModernEra
Indicates that the associated number or count applies specifically to the modern era timeframe, as opposed to historical or earlier periods.
- 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_69a49378b9c48190adbf5f62e5b7aca1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ace495348190aec66f35ea90bc89 |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa70973c8190adbf08302d1103a9 |
completed | March 1, 2026, 9:06 p.m. |
Created at: March 1, 2026, 7:38 p.m.