Triple
T2597382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 7th Infantry Division (United States) |
E58262
|
entity |
| Predicate | typeHistory |
P32919
|
FINISHED |
| Object | light infantry division |
—
|
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: light infantry division | Statement: [7th Infantry Division (United States), typeHistory, light infantry division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeHistory Context triple: [7th Infantry Division (United States), typeHistory, light infantry division]
-
A.
hasTypeHistory
chosen
Indicates that an entity is associated with a record or sequence of its past and present types or classifications over time.
-
B.
ownershipHistory
Indicates the sequence of past and present owners associated with an entity over time.
-
C.
upgradeHistory
Indicates the record of changes where one version, state, or configuration has been replaced or improved by another over time.
-
D.
includesChangeHistory
Indicates that the subject maintains or contains a record of past modifications or changes made to it.
-
E.
operatorHistory
Indicates a record of past actions, states, or changes associated with a particular operator over time.
- 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_69ab4ac14040819098b13f4a27d5c8ff |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd4548b1081909d28f88ea5e14202 |
completed | March 7, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69abd0d344988190a18dd93b13e002e6 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.