Triple
T4954814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1973–74 ABA season |
E111254
|
entity |
| Predicate | usedRule |
P25685
|
FINISHED |
| Object | three-point line |
—
|
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: three-point line | Statement: [1973–74 ABA season, usedRule, three-point line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedRule Context triple: [1973–74 ABA season, usedRule, three-point line]
-
A.
usesRulesFrom
Indicates that one entity applies, follows, or is governed by the rules defined or provided by another entity.
-
B.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
C.
usedInCase
Indicates that something (such as an item, method, or piece of information) is employed or applied within a particular case or instance.
-
D.
associatedWithRule
chosen
Indicates that an entity is linked or connected to a specific rule, such as being governed, constrained, or defined by that rule.
-
E.
usedAgainst
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71b945c0819082723712905f8295 |
completed | March 20, 2026, 4:11 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3beb008190852fd6150813b252 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:32 p.m.