Triple
T34699530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soccsksargen |
E1000327
|
entity |
| Predicate | hasFormerRegionalCenter |
P30576
|
FINISHED |
| Object | General Santos |
—
|
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: General Santos | Statement: [Soccsksargen, hasFormerRegionalCenter, General Santos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerRegionalCenter Context triple: [Soccsksargen, hasFormerRegionalCenter, General Santos]
-
A.
isInFormerRegion
Indicates that one entity is located within a geographic or administrative area that previously existed or had a different status or boundaries in the past.
-
B.
hadRegionalCenter
chosen
Indicates that an entity possessed, operated, or was associated with a specific regional center serving a defined geographic area.
-
C.
hasFormerSettlement
Indicates that a location previously contained a settlement that no longer exists or is no longer inhabited.
-
D.
isInFormerCapital
Indicates that an entity is located within a city that previously served as a capital but no longer holds that status.
-
E.
hasCentralRegion
Indicates that an entity possesses or is associated with a primary or central area within its overall structure or domain.
- 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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: May 3, 2026, 3:59 p.m.