Triple
T12269342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overcoming Law |
E292430
|
entity |
| Predicate | advocatesApproach |
P26857
|
FINISHED |
| Object | pragmatic approach to 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: pragmatic approach to law | Statement: [Overcoming Law, advocatesApproach, pragmatic approach to law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advocatesApproach Context triple: [Overcoming Law, advocatesApproach, pragmatic approach to law]
-
A.
advocates
Indicates that one entity publicly supports, recommends, or argues in favor of another entity or its interests.
-
B.
advocatesAgainst
Indicates that one entity actively opposes, argues against, or campaigns to prevent or stop another entity, action, or idea.
-
C.
approaches
Indicates that one entity moves closer in position or state to another entity or reference point.
-
D.
hasAdvocacyMethod
chosen
Indicates the method, strategy, or approach used to advocate for a cause, issue, or entity.
-
E.
formsApproachTo
Indicates that one entity develops or establishes a particular method, strategy, or way of dealing with or addressing another entity or situation.
- 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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9380a5e78819086bd4dfe9a83d1f5 |
completed | April 10, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69d91c4a66cc819083ce6fcaf5042af6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.