Triple
T26346730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolling Thunder |
E662793
|
entity |
| Predicate | legalInStandardMatches |
P155172
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Rolling Thunder, legalInStandardMatches, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalInStandardMatches Context triple: [Rolling Thunder, legalInStandardMatches, yes]
-
A.
legalStandardOftenIncludes
Indicates that a particular legal standard commonly or typically encompasses or contains another specified element, criterion, or requirement.
-
B.
legalIn
chosen
Indicates that an action, status, or entity is permitted or valid under the laws or regulations of a specified jurisdiction.
-
C.
legalStandardType
Indicates the specific type or category of legal standard that governs or applies to a given legal rule, decision, or evaluation.
-
D.
isStandardForLeague
Indicates that something conforms to the official rules, specifications, or norms established by a particular league.
-
E.
typicalMatchStipulation
Indicates that a condition or set of conditions is normally required or expected to be satisfied for a match or pairing between entities to be valid.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 26, 2026, 10:42 p.m.