Triple
T5326373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Base Charleston |
E123194
|
entity |
| Predicate | openedAsJointBase |
P63513
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Joint Base Charleston, openedAsJointBase, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsJointBase Context triple: [Joint Base Charleston, openedAsJointBase, 2010]
-
A.
openedAs
Indicates that one entity began operating, functioning, or being available to the public under the form, name, or role of another entity.
-
B.
openedInPart
Indicates that an entity was opened or made accessible only partially, rather than fully or completely.
-
C.
openedAsComplex
Indicates that one entity was inaugurated or began operation specifically as a multi-part or multi-use complex, rather than as a single standalone facility.
-
D.
openedIn
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
-
E.
openedAsBranchOf
Indicates that one entity was established and began operating as a branch or subsidiary location of another entity.
- 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_69bd46477f9081909d242a327d749466 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd86f20f008190be7b5848af05f2b8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd84561c7081909e5937c7816e492c |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd86f0cbfc8190b6665dd9b28d6345 |
completed | March 20, 2026, 5:42 p.m. |
Created at: March 20, 2026, 1:59 p.m.