Triple
T16433717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liver Bird |
E399129
|
entity |
| Predicate | materialUsedInStatues |
P1272
|
FINISHED |
| Object | copper (Royal Liver Building birds) |
—
|
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: copper (Royal Liver Building birds) | Statement: [Liver Bird, materialUsedInStatues, copper (Royal Liver Building birds)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: materialUsedInStatues Context triple: [Liver Bird, materialUsedInStatues, copper (Royal Liver Building birds)]
-
A.
statueMaterialDetail
Indicates that a statue is made of, or incorporates, a specific material with detailed characterization (e.g., type, composition, or quality).
-
B.
templeMaterial
Indicates that a temple is constructed from, or primarily composed of, a specified material.
-
C.
mainAltarMaterial
Indicates the material from which the main altar is made.
-
D.
materialUsed
chosen
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
E.
usesSculptureFor
Indicates that one entity employs or utilizes a sculpture for a particular purpose, function, or activity.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32ba01a1c8190b5a4700e2364ae63 |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.