Triple
T9137641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London 2012 Olympics brand identity |
E219241
|
entity |
| Predicate | designFee |
P87326
|
FINISHED |
| Object | 400000 GBP |
—
|
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: 400000 GBP | Statement: [London 2012 Olympics brand identity, designFee, 400000 GBP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designFee Context triple: [London 2012 Olympics brand identity, designFee, 400000 GBP]
-
A.
designBureau
Indicates that an entity functions as a design bureau responsible for planning, developing, or engineering designs for another entity or project.
-
B.
designLead
Indicates that one entity serves as the primary designer or person in charge of leading the design work for another entity or project.
-
C.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
D.
helpsDesign
Indicates that one entity assists or contributes to another entity’s design or design process.
-
E.
estimatedCost
Indicates the predicted or calculated monetary amount expected to be required for something, such as a project, item, or action.
- F. None of above. chosen
Provenance (4 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_69ca83e012288190a5771058adbaabd2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8efe3b88190a55a15827e6817a4 |
completed | April 1, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69cc6601d77881908299d58db6e64937 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc6a3c78388190a7436acc0e44ff55 |
completed | April 1, 2026, 12:43 a.m. |
Created at: March 30, 2026, 7:19 p.m.