Triple
T31329064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Optile bus network |
E798974
|
entity |
| Predicate | governingSector |
P201097
|
FINISHED |
| Object | public transport sector |
—
|
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: public transport sector | Statement: [Optile bus network, governingSector, public transport sector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingSector Context triple: [Optile bus network, governingSector, public transport sector]
-
A.
sectorGoverned
Indicates that a particular sector or domain is under the authority, control, or regulatory oversight of a specified governing entity.
-
B.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
C.
sectorOfOperation
Indicates the industry, domain, or field within which an entity conducts its primary activities or operations.
-
D.
regulatedSector
Indicates that an entity operates within an industry or domain that is subject to formal rules, oversight, and control by regulatory authorities.
-
E.
sectoralClassification
Indicates how an entity is categorized into a specific economic or industry sector within a classification scheme.
- 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffc7b4c7f88190b6357a44e7f0940f |
completed | May 9, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69ffc755f09c8190995ca00d97336988 |
completed | May 9, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69ffc7b41e688190ad3b86d87c38888e |
completed | May 9, 2026, 11:48 p.m. |
Created at: April 29, 2026, 9:16 p.m.