Triple
T26851262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuyonon |
E676063
|
entity |
| Predicate | secondaryAreaOfUse |
P180307
|
FINISHED |
| Object | mainland Palawan |
—
|
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: mainland Palawan | Statement: [Kuyonon, secondaryAreaOfUse, mainland Palawan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryAreaOfUse Context triple: [Kuyonon, secondaryAreaOfUse, mainland Palawan]
-
A.
secondaryLandUse
Indicates a secondary or additional way in which a piece of land is used, beyond its primary designated use.
-
B.
secondaryBuildingUse
Indicates how a building is used in a secondary or supplementary capacity in addition to its primary function.
-
C.
primaryUseArea
Indicates the main functional area or domain in which an entity is primarily used or applied.
-
D.
secondaryFunction
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
-
E.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
- 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_69eee9b9d7708190a15d7485709ae981 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
| PDg | Predicate description generation | batch_69f73adfd9a081908adae6bd59dfefb9 |
completed | May 3, 2026, 12:09 p.m. |
Created at: April 27, 2026, 5:17 a.m.