Triple
T14311835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erie doctrine |
E354850
|
entity |
| Predicate | twinAims |
P64674
|
FINISHED |
| Object | discouraging forum shopping |
—
|
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: discouraging forum shopping | Statement: [Erie doctrine, twinAims, discouraging forum shopping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: twinAims Context triple: [Erie doctrine, twinAims, discouraging forum shopping]
-
A.
twinType
Indicates that one entity is classified as a specific type or category of twin in relation to another entity.
-
B.
twinning
Indicates that two entities are paired or linked as twins, typically sharing a formally recognized, parallel, or closely matched relationship.
-
C.
aimOf
chosen
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
D.
twinOrder
Indicates the relative birth sequence or ordering between two twins within a twin pair.
-
E.
aimsToBalance
Indicates an intention or effort by one entity to bring multiple elements, forces, or conditions into a state of equilibrium.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de85b386d0819087d14f3ce84a1997 |
completed | April 14, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:12 a.m.