Triple
T7394402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Marine Corps Regimental Combat Team 1 |
E170584
|
entity |
| Predicate | roleInSecondBattleOfFallujah |
P28183
|
FINISHED |
| Object | major combat role |
—
|
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: major combat role | Statement: [U.S. Marine Corps Regimental Combat Team 1, roleInSecondBattleOfFallujah, major combat role]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInSecondBattleOfFallujah Context triple: [U.S. Marine Corps Regimental Combat Team 1, roleInSecondBattleOfFallujah, major combat role]
-
A.
roleDuringBlackHawkWar
Indicates the specific role, position, or function an entity held during the Black Hawk War.
-
B.
sideInBattleOfBadr
Indicates the role or allegiance an entity had on a particular side during the Battle of Badr.
-
C.
laterFoughtAlongside
Indicates that two entities, who were previously in some other relationship or context, subsequently fought on the same side as allies in a conflict or battle.
-
D.
sideInBattleOfYarmouk
Indicates that an entity participated as a side (belligerent) in the Battle of Yarmouk.
-
E.
notableBattleRole
chosen
Indicates the specific role or function an entity played in a notable or historically significant battle.
- 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_69c68a5f04188190ac266569c9280347 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2263b48819089319a2a2f0d3357 |
completed | March 27, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c6f0309cc88190b55d278969400294 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:09 p.m.