Triple
T24162230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R9 |
E598871
|
entity |
| Predicate | inspiredUseOfTerm |
P95447
|
FINISHED |
| Object | R9 as a generic label for top strikers wearing number 9 |
—
|
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: R9 as a generic label for top strikers wearing number 9 | Statement: [R9, inspiredUseOfTerm, R9 as a generic label for top strikers wearing number 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredUseOfTerm Context triple: [R9, inspiredUseOfTerm, R9 as a generic label for top strikers wearing number 9]
-
A.
inspiredTermMeaning
chosen
Indicates that one term’s meaning is derived from, modeled after, or conceptually influenced by another term.
-
B.
coinedTerm
Indicates that an entity originated and introduced a particular term or expression into use.
-
C.
usedTerm
Indicates that one entity employed, referenced, or applied a particular term in some context.
-
D.
inspiredByPhrase
Indicates that one entity’s creation, idea, or expression is motivated or shaped by the content or wording of a particular phrase.
-
E.
useOfTerm
Indicates that one entity employs or applies a specific term or expression in reference to another entity or context.
- 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_69e288cb0a3081909ef221744f274384 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:32 p.m.