Triple
T35130050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rule 53 – New Trial |
E1014411
|
entity |
| Predicate | hasGround |
P183167
|
FINISHED |
| Object | newly discovered evidence |
—
|
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: newly discovered evidence | Statement: [Rule 53 – New Trial, hasGround, newly discovered evidence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGround Context triple: [Rule 53 – New Trial, hasGround, newly discovered evidence]
-
A.
hasGroundPressure
Indicates that an entity exerts a specific amount of pressure on the ground or surface it is in contact with.
-
B.
hasGroundState
Indicates that an entity possesses a lowest-energy, most stable state in its energy configuration.
-
C.
hasGrounds
Indicates that one entity possesses or includes a physical area of land or outdoor space associated with it.
-
D.
usesGroundFor
Indicates that one entity makes functional or practical use of a particular ground, surface, or land area for its activities or purposes.
-
E.
usesGroundSystem
Indicates that one entity operates, relies on, or interacts with a particular ground-based system to perform its functions or services.
- 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f798387ea481909f51303f53a22e52 |
completed | May 3, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79798663481908d6bc48dd6a94ca6 |
completed | May 3, 2026, 6:44 p.m. |
Created at: May 3, 2026, 4:02 p.m.