Triple
T25099222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freeport Area of Bataan |
E628676
|
entity |
| Predicate | hasLocatorType |
P16808
|
FINISHED |
| Object | export-oriented enterprises |
—
|
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: export-oriented enterprises | Statement: [Freeport Area of Bataan, hasLocatorType, export-oriented enterprises]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocatorType Context triple: [Freeport Area of Bataan, hasLocatorType, export-oriented enterprises]
-
A.
haveType
chosen
Indicates that an entity belongs to or is classified under a specified type or category.
-
B.
hasMainLocationType
Indicates that an entity is associated with a primary or predominant type of location that characterizes where it is mainly situated or operates.
-
C.
hasDiscoveryType
Indicates the specific manner, method, or category by which something was discovered.
-
D.
hasLoadType
Indicates the type or category of load associated with an entity (e.g., electrical, mechanical, data, or other load classifications).
-
E.
hasStationTypeAt
Indicates that a specific type of station is present or assigned at a particular location or point.
- 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 18, 2026, 6:25 a.m.