Triple
T28110240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bondoc Peninsula |
E710467
|
entity |
| Predicate | projectsBetween |
P164049
|
FINISHED |
| Object | Ragay Gulf |
—
|
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: Ragay Gulf | Statement: [Bondoc Peninsula, projectsBetween, Ragay Gulf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectsBetween Context triple: [Bondoc Peninsula, projectsBetween, Ragay Gulf]
-
A.
projectsBetween
chosen
Indicates a relationship where something is projected or extends from one entity to another across an intervening space or set of entities.
-
B.
projectsOn
Indicates that one entity casts, directs, or extends itself onto the surface, area, or domain of another entity.
-
C.
collaborativeProjects
Indicates that two or more entities work together on shared projects or initiatives toward common goals.
-
D.
projectsInto
Indicates that one entity extends or maps its form, structure, or influence into another space, domain, or entity.
-
E.
productionProject
Indicates that an entity is involved in or associated with a specific production project, typically as part of its creation, development, or execution.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 9:10 p.m.