Triple
T28920416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Filinvest Technology Park – Calamba |
E733493
|
entity |
| Predicate | typicalLocators |
P203201
|
FINISHED |
| Object | electronics manufacturers |
—
|
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: electronics manufacturers | Statement: [Filinvest Technology Park – Calamba, typicalLocators, electronics manufacturers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLocators Context triple: [Filinvest Technology Park – Calamba, typicalLocators, electronics manufacturers]
-
A.
locates
Indicates that one entity determines, specifies, or identifies the position or place of another entity in space or within a given context.
-
B.
typicalUseLocation
Indicates the usual or most common location where an entity is used or operates.
-
C.
typicalControlLocation
Indicates the usual or standard physical location from which control or operation of something is exercised.
-
D.
typicalFeatures
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
-
E.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
- 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a013b78bde881909a082beced4e0157 |
completed | May 11, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_6a013acf45508190a999b208066072bd |
completed | May 11, 2026, 2:11 a.m. |
| PDg | Predicate description generation | batch_6a013b7808f08190979d68007e1882c6 |
completed | May 11, 2026, 2:14 a.m. |
Created at: April 28, 2026, 8:19 a.m.