Triple
T14131355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burgundy |
E350173
|
entity |
| Predicate | programOperator |
P179
|
FINISHED |
| Object | Privilege Club operator |
—
|
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: Privilege Club operator | Statement: [Burgundy, programOperator, Privilege Club operator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programOperator Context triple: [Burgundy, programOperator, Privilege Club operator]
-
A.
programOperation
Indicates an operation or action performed by, within, or upon a program in a computational or procedural context.
-
B.
operatorCode
Indicates that one entity is associated with a specific operator’s identifying code used to denote who performs or manages an operation or service.
-
C.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
D.
operator
chosen
Indicates that one entity functions as the operator (controller or handler) of another entity, such as a system, device, or process.
-
E.
typicalOperator
Indicates that an entity commonly or normally performs operations on, or acts upon, another entity in a standard or expected manner.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de610cece88190b4a86500677e5938 |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 11:03 p.m.