Triple
T25560401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advanced Clean Fleets regulation |
E640697
|
entity |
| Predicate | affectsStakeholder |
P142521
|
FINISHED |
| Object | port drayage operators |
—
|
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: port drayage operators | Statement: [Advanced Clean Fleets regulation, affectsStakeholder, port drayage operators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectsStakeholder Context triple: [Advanced Clean Fleets regulation, affectsStakeholder, port drayage operators]
-
A.
alsoAffects
chosen
Indicates that an action, condition, or change impacting one entity additionally impacts another entity as well.
-
B.
standAffected
Indicates that an entity is in a state or position of being impacted or influenced by another entity or event.
-
C.
affectedPerson
Indicates that a particular person is impacted or influenced by an event, action, or condition.
-
D.
affectedCompany
Indicates that a company is impacted or influenced by a particular event, action, or entity.
-
E.
governingBodyImpacted
Indicates that a governing body is affected or influenced by a particular action, event, or condition.
- 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_69e75dc1beb08190bac7d76b8d6e7bc4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 21, 2026, 3:45 p.m.