Triple
T15397071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gwadar Free Zone |
E368202
|
entity |
| Predicate | plannedActivity |
P29774
|
FINISHED |
| Object | light manufacturing |
—
|
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: light manufacturing | Statement: [Gwadar Free Zone, plannedActivity, light manufacturing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedActivity Context triple: [Gwadar Free Zone, plannedActivity, light manufacturing]
-
A.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
-
B.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
-
C.
plannedEntry
Indicates that an entity is scheduled or intended to enter another entity, context, or location at a planned future time.
-
D.
plannedVia
Indicates that something is arranged, organized, or scheduled by means of a particular method, process, or intermediary.
-
E.
partOfPlan
chosen
Indicates that one entity is included as a component or step within a broader plan or strategy.
- 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e8c5d40819086622b70edcb6294 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.