Triple
T7815935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grady Wilson |
E181007
|
entity |
| Predicate | oftenServesAs |
P23174
|
FINISHED |
| Object | comic relief |
—
|
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: comic relief | Statement: [Grady Wilson, oftenServesAs, comic relief]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenServesAs Context triple: [Grady Wilson, oftenServesAs, comic relief]
-
A.
alsoServesAs
Indicates that one entity has an additional role, function, or identity that it fulfills simultaneously with its primary one.
-
B.
typicallyServedAs
chosen
Indicates that something is most commonly presented, used, or offered in a particular role, form, or function.
-
C.
alsoServedBy
Indicates that the same service, function, or role is additionally provided or fulfilled by another entity alongside the primary one.
-
D.
alsoServes
Indicates that an entity, in addition to its primary role or function, provides service or support to another specified entity or group.
-
E.
servesAsQualifierFor
Indicates that one entity functions as a qualifier or modifier that refines, restricts, or specifies the meaning or scope 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_69ca828153f48190bdb27ac46f8e0745 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf96d1f088190a1d005ffb019afe9 |
completed | March 30, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69cae91687788190af9cb7aaa996d291 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:39 p.m.