Triple
T7358738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Java economic region |
E169691
|
entity |
| Predicate | dominantSector |
P71
|
FINISHED |
| Object | 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: manufacturing | Statement: [Java economic region, dominantSector, manufacturing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantSector Context triple: [Java economic region, dominantSector, manufacturing]
-
A.
dominatedSector
Indicates that one entity exercises prevailing control or influence over a particular sector relative to others.
-
B.
hasServiceSectorDominance
Indicates that the service sector constitutes the largest or most influential portion of an entity’s overall economic or operational activity.
-
C.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
D.
notableSector
Indicates that an entity is particularly prominent, influential, or significant within a specified sector or industry.
-
E.
sector
chosen
Indicates that an entity operates in, belongs to, or is associated with a particular economic or industrial sector.
- 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_69c68a59f2288190877ca15c19b1e822 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f26d6d6081909c7272a9ccae0d97 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f02d36108190bcb34a95e6a30bd7 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:06 p.m.