Triple
T27160077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Conference (no divisions) |
E682635
|
entity |
| Predicate | mayBeAppliedIn |
P3306
|
FINISHED |
| Object | basketball leagues |
—
|
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: basketball leagues | Statement: [Eastern Conference (no divisions), mayBeAppliedIn, basketball leagues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeAppliedIn Context triple: [Eastern Conference (no divisions), mayBeAppliedIn, basketball leagues]
-
A.
appliesAt
chosen
Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
-
B.
appliesFrom
Indicates that a rule, condition, or effect begins to be applicable starting from a specific point in time or state.
-
C.
appliesVia
Indicates that an action, rule, or effect is carried out, implemented, or achieved through a specified method, medium, or mechanism.
-
D.
appliedWhen
Indicates the condition, time, or circumstances under which something (such as a rule, action, or effect) becomes applicable or is carried out.
-
E.
mayApply
Indicates that an entity is permitted or eligible to submit or use something (such as a rule, action, or resource) under certain conditions.
- 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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 9:18 a.m.