Triple
T6489559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ordre du Mérite des Transports |
E148000
|
entity |
| Predicate | sectorRecognized |
P71028
|
FINISHED |
| Object | transport policy |
—
|
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: transport policy | Statement: [Ordre du Mérite des Transports, sectorRecognized, transport policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectorRecognized Context triple: [Ordre du Mérite des Transports, sectorRecognized, transport policy]
-
A.
sectorCode
Indicates the classification code that identifies the economic or organizational sector associated with an entity or activity.
-
B.
sectorServed
Indicates the industry or economic sector that an entity primarily serves or targets with its activities, products, or services.
-
C.
sectorRepresented
Indicates that an entity serves as a representative or proxy for a particular sector (such as an industry, domain, or market segment).
-
D.
isSectorSpecific
Indicates that something is tailored or restricted to a particular industry or sector rather than being generally applicable.
-
E.
sectorIncludes
Indicates that a broader sector encompasses or contains a specified sub-sector, area, or component within its scope.
- 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_69c009088f3081909cd467b05919de30 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a9926fc81909db0f390e385e97d |
completed | March 22, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69c06740bebc81909d9d6956baa2bcb9 |
completed | March 22, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69c067f1ef148190bc0355abe83f7e16 |
completed | March 22, 2026, 10:06 p.m. |
Created at: March 22, 2026, 4:52 p.m.