Triple
T38456755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manila–Puerto Princesa |
E912338
|
entity |
| Predicate | countryCapitalAtOrigin |
P160390
|
FINISHED |
| Object | Manila |
E7896
|
NE 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: Manila | Statement: [Manila–Puerto Princesa, countryCapitalAtOrigin, Manila]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryCapitalAtOrigin Context triple: [Manila–Puerto Princesa, countryCapitalAtOrigin, Manila]
-
A.
countryCapitalUntil
Indicates that a specified city served as the capital of a given country up to (but not necessarily including) a particular end date or time period.
-
B.
countryCapitalLocatedOn
Indicates that the capital city of a country is situated on or directly adjacent to a specified geographic feature (such as a river, coast, or lake).
-
C.
countryCapitalSince
Indicates that a specified city has served as the capital of a given country starting from a particular point in time.
-
D.
destinationCapitalOf
chosen
Indicates that a location serves as the capital city of the specified destination or region.
-
E.
countryCapitalLocatedWithin
Indicates that the capital city of a country is geographically situated within the boundaries of that country.
- F. None of above.
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_69f76e84e2dc81908badf05b3aafa9ea |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a42e07b7ce08190a4defc5bb9fefd0b |
completed | June 29, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.