Triple
T10679219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 369th Infantry Regiment |
E251699
|
entity |
| Predicate | hadWhiteOfficers |
P95269
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [369th Infantry Regiment, hadWhiteOfficers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadWhiteOfficers Context triple: [369th Infantry Regiment, hadWhiteOfficers, true]
-
A.
officersAre
Indicates that certain individuals hold the role or position of officers within a specified group, organization, or context.
-
B.
officersServeAs
Indicates that certain individuals hold and perform the role or duties of officers within a particular organization or context.
-
C.
hasJudicialOfficer
Indicates that an entity is associated with or served by a specific judicial officer (such as a judge or magistrate) responsible for legal or court-related functions.
-
D.
officersCalled
Indicates that law enforcement officers were summoned or notified to respond to a situation or incident.
-
E.
hasMinorityIn
Indicates that one entity holds a non-controlling, minority ownership or stake in another entity.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fcc03dc4819080a6211a2bfaaf0a |
completed | April 9, 2026, 1:11 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8a93208190a573061387e2aebb |
completed | April 8, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69d6df47899481909ac0e518d94883cb |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 9:10 p.m.