Triple
T398531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geneva metropolitan area |
E9225
|
entity |
| Predicate | laborMarket |
P10964
|
FINISHED |
| Object | integrated Franco-Swiss labor market |
—
|
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: integrated Franco-Swiss labor market | Statement: [Geneva metropolitan area, laborMarket, integrated Franco-Swiss labor market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laborMarket Context triple: [Geneva metropolitan area, laborMarket, integrated Franco-Swiss labor market]
-
A.
laborProvision
Indicates the provision or supply of labor or workforce from one party to another for work or services.
-
B.
laborSystem
Indicates the type or structure of work organization, employment arrangements, and labor relations that govern how work is performed and managed.
-
C.
market
Indicates the act of promoting, advertising, or selling a product, service, or idea to potential buyers or target audiences.
-
D.
sector
Indicates that an entity operates in, belongs to, or is associated with a particular economic or industrial sector.
-
E.
economicTrend
Indicates the general direction or pattern of economic activity or conditions over a period of time.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ec8bcf708190b62e15806159ceb1 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96d17d08190878d3a68b17d51ca |
completed | Feb. 28, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69a2ea4545608190898436c72e10f39d |
completed | Feb. 28, 2026, 1:14 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.