Triple
T630650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camp Pendleton, California |
E15917
|
entity |
| Predicate | supportsUnitType |
P13867
|
FINISHED |
| Object | ground combat units |
—
|
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: ground combat units | Statement: [Camp Pendleton, California, supportsUnitType, ground combat units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsUnitType Context triple: [Camp Pendleton, California, supportsUnitType, ground combat units]
-
A.
hostsUnitType
chosen
Indicates that one entity serves as a location or platform that accommodates or contains a specified type of unit.
-
B.
typeOfSupport
Indicates the kind or category of assistance, help, or backing provided in a given context.
-
C.
isSupportedBy
Indicates that an entity is upheld, sustained, or enabled by another entity, which provides necessary assistance, resources, or justification.
-
D.
supportsProjectType
Indicates that one entity is capable of handling, accommodating, or being compatible with a specified type of project.
-
E.
typeOfUnit
Indicates that one entity specifies the kind or category of measurement unit that the other entity belongs to.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49ec171008190ab91dee86e9279af |
completed | March 1, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69a49d030c648190ba1a02301b45f694 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.