Triple
T26414473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lowe Post |
E664046
|
entity |
| Predicate | featuresGuests |
P44542
|
FINISHED |
| Object | NBA players |
—
|
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: NBA players | Statement: [The Lowe Post, featuresGuests, NBA players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresGuests Context triple: [The Lowe Post, featuresGuests, NBA players]
-
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.
featuresGuestContributions
Indicates that an entity includes or showcases content, work, or input provided by external guests rather than its primary or regular contributors.
-
D.
notableHosts
Indicates that one or more entities are recognized as prominent or distinguished hosts associated with another entity or event.
-
E.
featuresVariousArtists
Indicates that something (typically a creative work) includes contributions from multiple distinct artists rather than a single primary artist.
- 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_69ee883a04ec81908883c4559f8c7e24 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 26, 2026, 11:40 p.m.