Triple
T22715519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frog Bridge (Thread City Crossing) |
E561721
|
entity |
| Predicate | materialOfFrogSculptures |
P136410
|
FINISHED |
| Object | bronze |
—
|
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: bronze | Statement: [Frog Bridge (Thread City Crossing), materialOfFrogSculptures, bronze]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: materialOfFrogSculptures Context triple: [Frog Bridge (Thread City Crossing), materialOfFrogSculptures, bronze]
-
A.
materialDepicted
Indicates that a work or representation visually portrays or includes a particular material as part of its subject.
-
B.
statueMaterialDetail
Indicates that a statue is made of, or incorporates, a specific material with detailed characterization (e.g., type, composition, or quality).
-
C.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
D.
hasSculptureMaterial
chosen
Indicates that a sculpture is made from, or incorporates, a specified material.
-
E.
stringMaterialDepicted
Indicates that one entity is a string material that is visually represented or depicted 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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1790ca59881909064d49f331fb711 |
completed | April 29, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:18 p.m.