Triple
T33221441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trent Tucker Rule |
E850430
|
entity |
| Predicate | ruleFormat |
P130
|
FINISHED |
| Object | written in NBA rulebook |
—
|
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: written in NBA rulebook | Statement: [Trent Tucker Rule, ruleFormat, written in NBA rulebook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruleFormat Context triple: [Trent Tucker Rule, ruleFormat, written in NBA rulebook]
-
A.
styleOfRule
Indicates the stylistic or formatting convention that a particular rule follows or is expressed in.
-
B.
notationRule
Indicates a rule or convention governing how something should be represented or written in a particular notation system.
-
C.
rulesText
Indicates that one entity provides the explicit written rules, instructions, or governing text that define how another entity operates or should be used.
-
D.
format
chosen
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
E.
rulesBy
Indicates that one entity governs, controls, or exercises authoritative power over another entity.
- 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:30 a.m.