Triple
T23034516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feherty |
E573556
|
entity |
| Predicate | featuresGuestsFrom |
P44542
|
FINISHED |
| Object | 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: sports | Statement: [Feherty, featuresGuestsFrom, sports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresGuestsFrom Context triple: [Feherty, featuresGuestsFrom, sports]
-
A.
typicalGuests
chosen
Indicates the usual or most common guests associated with a particular host, place, or event.
-
B.
guestStar
Indicates that one entity appears in a limited, special, or featured role within another entity’s production, event, or context, without being a regular or primary participant.
-
C.
notableHosts
Indicates that one or more entities are recognized as prominent or distinguished hosts associated with another entity or event.
-
D.
recurringGuestIn
Indicates that an entity appears repeatedly as a guest in a particular context, such as a show, event, or series.
-
E.
guestOnBoard
Indicates that an entity is currently present as a guest aboard a vehicle, vessel, or similar conveyance.
- 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_69e245b911188190bc3d96326c847969 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18483e5848190977b1bdb1b83d187 |
completed | April 29, 2026, 4:09 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:53 p.m.