Triple
T24103409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RPLC |
E597148
|
entity |
| Predicate | previousFacility |
P35178
|
FINISHED |
| Object | Clark Air Base |
—
|
NE NERFINISHED |
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: Clark Air Base | Statement: [RPLC, previousFacility, Clark Air Base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousFacility Context triple: [RPLC, previousFacility, Clark Air Base]
-
A.
legacyFacilityOf
chosen
Indicates that one facility is an older, predecessor, or superseded version of another facility within the same organizational or operational context.
-
B.
currentFacility
Indicates that an entity is presently located in, assigned to, or operating within a particular facility.
-
C.
successorFacilityLocation
Indicates that one facility location directly follows or replaces another in a sequence or succession of locations.
-
D.
successorFacility
Indicates that one facility directly follows and replaces another in function, ownership, or operation.
-
E.
formerHomeFacility
Indicates that an entity was previously housed, based, or operated in a particular facility but no longer is.
- 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_69e288c60f9c8190af948d7354aedbeb |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dd2ad01881909aa5a3c300009086 |
completed | April 29, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11 p.m.