Triple
T17146430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eddie Brown |
E416102
|
entity |
| Predicate | rulesVariation |
P67886
|
FINISHED |
| Object | arena football |
—
|
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: arena football | Statement: [Eddie Brown, rulesVariation, arena football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulesVariation Context triple: [Eddie Brown, rulesVariation, arena football]
-
A.
rulesVariantOf
chosen
Indicates that one set of rules is a modified or alternative version derived from another set of rules.
-
B.
policyVariation
Indicates that one policy differs from another in certain terms, conditions, or parameters.
-
C.
hasServiceVariations
Indicates that a service is offered in multiple distinct versions, options, or configurations that differ in some defined characteristics.
-
D.
attributeVariesBy
Indicates that a particular attribute can take on different values depending on another variable, context, or condition.
-
E.
governsVariant
Indicates a regulatory relationship where one entity controls, influences, or determines the behavior or state of a specific variant of 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f2db20d48190b5d69ccf89f3bc42 |
completed | April 18, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.