Triple
T29344845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romont SO |
E744139
|
entity |
| Predicate | hasTertiarySectorEmployment |
P69121
|
FINISHED |
| Object | services |
—
|
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: services | Statement: [Romont SO, hasTertiarySectorEmployment, services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTertiarySectorEmployment Context triple: [Romont SO, hasTertiarySectorEmployment, services]
-
A.
hasTertiaryEconomicSector
chosen
Indicates that an entity participates in or possesses activities belonging to the tertiary (service) sector of the economy, such as services rather than primary or secondary production.
-
B.
hasOccupationSector
Indicates that an entity’s occupation belongs to or is categorized within a particular economic or professional sector.
-
C.
hasIndustrialEmployer
Indicates that an entity is employed by, or has an employment relationship with, an industrial organization or company.
-
D.
hasSecondaryIndustry
Indicates that an entity is associated with an additional, non-primary industry in which it operates or participates.
-
E.
hasMajorEmployerType
Indicates the type or category of major employer associated with an entity.
- 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 28, 2026, 2:01 p.m.