Triple
T27059031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brabo Fountain |
E684983
|
entity |
| Predicate | depictsLegend |
P1581
|
FINISHED |
| Object | legend of the giant Druon Antigoon |
—
|
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: legend of the giant Druon Antigoon | Statement: [Brabo Fountain, depictsLegend, legend of the giant Druon Antigoon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictsLegend Context triple: [Brabo Fountain, depictsLegend, legend of the giant Druon Antigoon]
-
A.
mentionsLegend
Indicates that one entity makes reference to or cites a legendary figure, story, or concept associated with another entity.
-
B.
labelDepicts
Indicates that one entity serves as a label or caption that visually or textually represents, illustrates, or describes another entity.
-
C.
depicts
chosen
Indicates that one entity visually represents, portrays, or shows another entity.
-
D.
legendStatus
Indicates that an entity holds, is assigned, or is associated with a particular legend-related status or classification.
-
E.
hasLegendAssociatedWith
Indicates that something is connected to or accompanied by a traditional story, myth, or legend.
- 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 8:20 a.m.