Triple
T36485252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LEE |
E898917
|
entity |
| Predicate | grapples |
P47753
|
FINISHED |
| Object | Power Data Grapple Fixture |
—
|
NE NERFINISHED |
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: Power Data Grapple Fixture | Statement: [LEE, grapples, Power Data Grapple Fixture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grapples Context triple: [LEE, grapples, Power Data Grapple Fixture]
-
A.
grapplingAllowed
Indicates that engaging in grappling (close-quarters holds, clinches, or wrestling maneuvers) between the involved parties is permitted.
-
B.
tackles
Indicates that one entity forcefully brings another entity to the ground or physically stops their movement, typically in a competitive or confrontational context.
-
C.
confronts
chosen
Indicates that one entity directly faces and challenges another, often in opposition or dispute.
-
D.
inning
Indicates a specific segment or period within a game during which a defined portion of play or action occurs.
-
E.
engagesInCyclicalStruggleWith
Indicates a relationship in which two entities are locked in a recurring, back-and-forth conflict or opposition that repeats over time.
- 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.