Triple
T17060774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2nd Battalion, 1st Marines |
E413950
|
entity |
| Predicate | hasCommonName |
P570
|
FINISHED |
| Object | 2/1 |
E413950
|
NE 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: 2/1 | Statement: [2nd Battalion, 1st Marines, hasCommonName, 2/1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 2/1 Context triple: [2nd Battalion, 1st Marines, hasCommonName, 2/1]
-
A.
2/1
chosen
2/1 is the commonly used shorthand nickname for the U.S. Marine Corps infantry unit 2nd Battalion, 1st Marines.
-
B.
2/8
2/8 is a battalion-sized infantry unit of the United States Marine Corps known for its combat deployments and role within the 8th Marine Regiment.
-
C.
2/6
2/6 is a battalion of the United States Marine Corps known for its infantry combat role and participation in major military operations.
-
D.
2/7
2/7 is a battalion-sized infantry unit of the United States Marine Corps known for its combat deployments and service in major conflicts.
-
E.
2/4
2/4 is a battalion of the United States Marine Corps known as the 2nd Battalion, 4th Marines, an infantry unit with a long history of combat deployments.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3db7d2dc48190816388570fa31c2e |
completed | April 18, 2026, 7:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0139f346f0819094a430a11e361bac |
completed | May 11, 2026, 2:07 a.m. |
Created at: April 10, 2026, 5:34 a.m.