Triple
T26572937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trucking Unlimited |
E666872
|
entity |
| Predicate | areaOfLawImpact |
P39579
|
FINISHED |
| Object | competition law |
—
|
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: competition law | Statement: [Trucking Unlimited, areaOfLawImpact, competition law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areaOfLawImpact Context triple: [Trucking Unlimited, areaOfLawImpact, competition law]
-
A.
impactOnLaw
chosen
Indicates the effect or influence that one entity, event, or action has on laws, legal rules, or the legal system.
-
B.
notableAreaOfLaw
Indicates that a person or entity is particularly recognized or distinguished in a specific field or area of law.
-
C.
legalArea
Indicates the specific field or branch of law that a legal matter, case, or document pertains to.
-
D.
legalBackground
Indicates that an entity has education, training, or experience related to law or the legal profession.
-
E.
legalDoctrineInfluenced
Indicates that one legal doctrine has shaped, informed, or contributed to the development or interpretation of another legal doctrine.
- 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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 1:59 a.m.