Triple
T17072471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pi’erre Bourne |
E414255
|
entity |
| Predicate | hasProducerTagSource |
P75823
|
FINISHED |
| Object | sample from The Jamie Foxx Show |
—
|
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: sample from The Jamie Foxx Show | Statement: [Pi’erre Bourne, hasProducerTagSource, sample from The Jamie Foxx Show]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProducerTagSource Context triple: [Pi’erre Bourne, hasProducerTagSource, sample from The Jamie Foxx Show]
-
A.
hasProducerTag
chosen
Indicates that an entity is associated with a tag identifying it as a producer or related to production.
-
B.
hasProducer
Indicates that one entity serves as the producer or creator responsible for making or manufacturing another entity.
-
C.
hasProducerAlias
Indicates that an entity has an alternative name or alias specifically used in the role of producer.
-
D.
hasMessageSender
Indicates that one entity is the sender or originator of a given message.
-
E.
hasTagLength
Indicates that an entity is associated with a tag whose length (typically in characters) has a specified value or satisfies a given constraint.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc1b7d48190979a848b4188cb22 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.