Triple
T2597384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 7th Infantry Division (United States) |
E58262
|
entity |
| Predicate | activation |
P7730
|
FINISHED |
| Object | World War I era |
—
|
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: World War I era | Statement: [7th Infantry Division (United States), activation, World War I era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activation Context triple: [7th Infantry Division (United States), activation, World War I era]
-
A.
activationMechanism
Indicates the process or method by which one entity initiates, triggers, or enables the activity or functioning of another entity.
-
B.
activationTime
Indicates the specific point in time at which an entity, process, or function becomes active or starts operating.
-
C.
activity
Indicates that an entity is engaged in or performing a particular action, behavior, or process.
-
D.
triggered
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
E.
activeFrom
chosen
Indicates the starting point in time from which an entity or relationship is considered active or in effect.
- 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.