Triple
T6350851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rule 33 |
E142865
|
entity |
| Predicate | allowsGrounds |
P273
|
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 33, allowsGrounds, newly discovered evidence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsGrounds Context triple: [Rule 33, allowsGrounds, newly discovered evidence]
-
A.
hasGrounds
Indicates that one entity possesses or includes a physical area of land or outdoor space associated with it.
-
B.
coversGrounds
Indicates that one entity extends over, occupies, or lies across the surface area of another entity (typically land or grounds).
-
C.
listsGrounds
Indicates that one entity enumerates or specifies the reasons, bases, or justifications (grounds) associated with another entity.
-
D.
allows
chosen
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
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.
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_69c008d6dcbc8190aa1c2f1fd8916b42 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c067dc2790819084aaf7067dc25733 |
completed | March 22, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69c060ea1a988190889e47b7e0c819b8 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:31 p.m.