Triple
T32930018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Negeri Sembilan monarchy |
E842375
|
entity |
| Predicate | historicalOriginArea |
P201038
|
FINISHED |
| Object | Pagaruyung |
—
|
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: Pagaruyung | Statement: [Negeri Sembilan monarchy, historicalOriginArea, Pagaruyung]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalOriginArea Context triple: [Negeri Sembilan monarchy, historicalOriginArea, Pagaruyung]
-
A.
historicalOrigin
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
-
B.
historicalRegion
Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
-
C.
historicalOriginCountry
Indicates the country from which something originally came or first emerged in a historical context.
-
D.
historicalRegionOfInfluence
Indicates that one entity was historically within the geographic, political, or cultural sphere of influence of another entity.
-
E.
historicalAdministrativeRegionName
Indicates the name assigned to an administrative region as it existed during a specific historical period.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffc3f0b19c8190b5a749bc3cad21dd |
completed | May 9, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69ffc1b882808190932b2d43ea5537c9 |
completed | May 9, 2026, 11:22 p.m. |
| PDg | Predicate description generation | batch_69ffc3eed97c819085c06ffe3699ff38 |
completed | May 9, 2026, 11:31 p.m. |
Created at: May 1, 2026, 1:20 a.m.