Triple
T11815931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swan |
E280999
|
entity |
| Predicate | isSymbolIn |
P89328
|
FINISHED |
| Object | European culture |
—
|
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: European culture | Statement: [Swan, isSymbolIn, European culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSymbolIn Context triple: [Swan, isSymbolIn, European culture]
-
A.
isSameSymbolAs
Indicates that two entities represent the identical symbol or sign, regardless of their specific instances or contexts.
-
B.
isRelatedSymbol
Indicates that one symbol has a defined relationship or association with another symbol, such as similarity, correspondence, or functional connection.
-
C.
appearsWithSymbol
Indicates that one entity is shown or presented together with a particular symbol in the same visual or contextual setting.
-
D.
symbolizedIn
chosen
Indicates that one entity serves as a symbol or representation of another entity.
-
E.
symbolicallyUses
Indicates that one entity employs another as a symbol or representation to convey meaning, ideas, or associations rather than for its literal or practical function.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a658f918819092c2db05fe2ab0ce |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a24e9a088190aff7932d1ff93dbf |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.