Triple
T15799735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subic Bay Metropolitan Authority |
E383065
|
entity |
| Predicate | typeOfFreeport |
P120064
|
FINISHED |
| Object | special economic zone |
—
|
LITERAL 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: special economic zone | Statement: [Subic Bay Metropolitan Authority, typeOfFreeport, special economic zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfFreeport Context triple: [Subic Bay Metropolitan Authority, typeOfFreeport, special economic zone]
-
A.
typeOfPortFacility
Indicates that one port facility is classified as a specific type or category of port facility in relation to another.
-
B.
typeOfReserve
Indicates that one entity is classified as a specific kind or category of reserve in relation to another entity.
-
C.
typeOfFIU
Indicates that one entity is classified as a specific type or category of Financial Intelligence Unit (FIU) in relation to another entity.
-
D.
berthType
Indicates the specific kind or category of berth associated with an entity, such as the type of sleeping or docking space provided.
-
E.
freightType
Indicates the category or mode of freight associated with a shipment or transport activity.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4e135b08190b736e77bac5e2bff |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e006b17f7881908b8c7a37f0af4581 |
completed | April 15, 2026, 9:44 p.m. |
Created at: April 10, 2026, 4:48 a.m.