Triple
T585778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Corps Recruit Depot San Diego |
E15152
|
entity |
| Predicate | branchOfServiceFocus |
P15908
|
FINISHED |
| Object | enlisted personnel |
—
|
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: enlisted personnel | Statement: [Marine Corps Recruit Depot San Diego, branchOfServiceFocus, enlisted personnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: branchOfServiceFocus Context triple: [Marine Corps Recruit Depot San Diego, branchOfServiceFocus, enlisted personnel]
-
A.
serviceBranch
Indicates the military or organizational branch in which an entity serves or is affiliated.
-
B.
serviceOf
Indicates that one entity performs, provides, or fulfills a function or duty on behalf of another entity.
-
C.
missionFocus
Indicates that an entity’s primary attention, effort, or resources are directed toward a particular mission, goal, or objective.
-
D.
sectorServed
Indicates the industry or economic sector that an entity primarily serves or targets with its activities, products, or services.
-
E.
focusesOn
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b9a46388190a094b9ebf8dec397 |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494c9315c8190a773e8e00737d8a0 |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985ada988190aaea628a9b55bca4 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:33 p.m.