Triple
T17514966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amata Industrial Park |
E426543
|
entity |
| Predicate | commonBusinessLanguage |
P33549
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Amata Industrial Park, commonBusinessLanguage, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonBusinessLanguage Context triple: [Amata Industrial Park, commonBusinessLanguage, English]
-
A.
typicalLanguageUse
Indicates that one entity is the language most commonly or habitually used by another entity in ordinary communication or contexts.
-
B.
languageOfCommunications
chosen
Indicates that a specified language is used as the medium for communications associated with an entity or interaction.
-
C.
commonLabel
Indicates that two or more entities share the same label or designation.
-
D.
overarchingLanguage
Indicates that one language serves as the primary or dominant linguistic framework governing or unifying other languages or language varieties in a given context.
-
E.
commonLevel
Indicates that two or more entities share the same level, rank, or hierarchical position within a given system or structure.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4525fa0c48190b42b36c40db7ed7f |
completed | April 19, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.