Triple
T3122024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The X Factor (franchise) |
E65204
|
entity |
| Predicate | typicalPrize |
P26432
|
FINISHED |
| Object | recording contract with major label |
—
|
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: recording contract with major label | Statement: [The X Factor (franchise), typicalPrize, recording contract with major label]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPrize Context triple: [The X Factor (franchise), typicalPrize, recording contract with major label]
-
A.
prizeType
Indicates the specific category or kind of prize associated with an entity or event.
-
B.
typicalAwardAmount
Indicates the usual or most common amount of an award given in this relationship.
-
C.
typicalAwardType
chosen
Indicates the usual or most common type or category of award associated with a given entity or context.
-
D.
typicalAwardedBy
Indicates the usual or standard agent (such as a person or organization) that confers or grants a particular award.
-
E.
prizeContext
Indicates the situational or contextual circumstances under which a prize is awarded, considered, or relevant.
- 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_69ad8580c72481909672d37acf647893 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada52ab05c819088204bbb608c837c |
completed | March 8, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69ad9df62e548190b053e1478deed467 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.