Triple
T13725194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The X Factor (Georgia) |
E329135
|
entity |
| Predicate | usesFormatElement |
P23479
|
FINISHED |
| Object | auditions |
—
|
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: auditions | Statement: [The X Factor (Georgia), usesFormatElement, auditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFormatElement Context triple: [The X Factor (Georgia), usesFormatElement, auditions]
-
A.
hasFormatElement
chosen
Indicates that one entity includes, is composed of, or is associated with a specific structural or formatting component of its overall format.
-
B.
usedInFormat
Indicates that something (such as a method, standard, or component) is employed or applied within a particular format.
-
C.
usedFormat
Indicates that one entity employs or applies a particular format or representation in relation to another entity.
-
D.
hasFormatCurrent
Indicates that an entity is available or expressed in the currently used or most up-to-date format.
-
E.
definesFormatFor
Indicates that one entity specifies or establishes the format or structural pattern to be used by 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de01f52e748190b49c34e10ab8ac34 |
completed | April 14, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:55 p.m.