Triple
T843947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5th Marine Division |
E18235
|
entity |
| Predicate | supportElement |
P16415
|
FINISHED |
| Object | artillery regiment |
—
|
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: artillery regiment | Statement: [5th Marine Division, supportElement, artillery regiment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportElement Context triple: [5th Marine Division, supportElement, artillery regiment]
-
A.
supportBase
Indicates that one entity serves as a foundational or backing structure that physically or functionally supports another entity.
-
B.
support
Indicates that one entity provides assistance, endorsement, or backing to another entity or its actions.
-
C.
providesSupportTo
chosen
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
-
D.
supportedAct
Indicates that one entity provided assistance, endorsement, or backing for a particular action or activity performed by another entity.
-
E.
supportedSide
Indicates that one entity backed, favored, or provided assistance to a particular side or party in a conflict, dispute, or competition.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac07fedc8190ab05595f25c1792f |
completed | March 1, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7f396c8190aa8b8dfbe0b4f732 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.