Triple
T12038969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No harm, no foul |
E286611
|
entity |
| Predicate | extendedUse |
P38557
|
FINISHED |
| Object | everyday conversation beyond sports |
—
|
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: everyday conversation beyond sports | Statement: [No harm, no foul, extendedUse, everyday conversation beyond sports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendedUse Context triple: [No harm, no foul, extendedUse, everyday conversation beyond sports]
-
A.
expandedUseOf
chosen
Indicates that something is being applied, implemented, or utilized more broadly or extensively than before.
-
B.
extendedIn
Indicates that one entity continues, prolongs, or expands the scope, duration, or range of another entity.
-
C.
extendedInCase
Indicates that one entity is lengthened, prolonged, or expanded when a particular condition or case applies.
-
D.
extendedFor
Indicates that something has been lengthened in duration, scope, or extent specifically for the benefit or use of another entity.
-
E.
extendedOn
Indicates that one entity continues, prolongs, or expands the duration, scope, or effect of another entity beyond its original limit.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bac9e08190aa1a99c835f29542 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.