Triple
T3377732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Corsair |
E71106
|
entity |
| Predicate | tattooSymbolism |
P129
|
FINISHED |
| Object | sign of the Corsair |
—
|
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: sign of the Corsair | Statement: [the Corsair, tattooSymbolism, sign of the Corsair]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tattooSymbolism Context triple: [the Corsair, tattooSymbolism, sign of the Corsair]
-
A.
emblemSymbolism
Indicates that one entity serves as an emblem whose design or features symbolically represent or convey meanings about another entity.
-
B.
clothingSymbolism
Indicates how clothing or attire conveys symbolic meaning, such as status, identity, emotion, or cultural significance, within a given context.
-
C.
starColorSymbolism
Indicates how the color of a star is associated with particular symbolic meanings or themes.
-
D.
symbolizes
chosen
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
E.
iconographyType
Indicates the specific kind or category of visual symbolism or imagery used to represent something.
- 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2e8d1988190b6fb6c4c5502f25f |
completed | March 8, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69ada433059881908e46f38cc5f40a32 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.