Triple
T4116453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of Gibraltar |
E90302
|
entity |
| Predicate | castleSymbolism |
P34702
|
FINISHED |
| Object | fortress |
—
|
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: fortress | Statement: [Flag of Gibraltar, castleSymbolism, fortress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: castleSymbolism Context triple: [Flag of Gibraltar, castleSymbolism, fortress]
-
A.
castleBuilt
Indicates that a castle has been constructed or established, typically by a specific agent or during a particular time period.
-
B.
castleBuiltFor
Indicates that a castle was constructed specifically for the benefit, use, or commission of a particular person, group, or purpose.
-
C.
castleOverlooks
Indicates that a castle is positioned so that it has a clear, elevated view over a particular area, object, or landscape.
-
D.
emblemSymbolism
chosen
Indicates that one entity serves as an emblem whose design or features symbolically represent or convey meanings about another entity.
-
E.
architecturalSymbol
Indicates that one entity serves as a symbolic or emblematic representation of another within an architectural context.
- 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_69aed95c080881908125e30c5dcdc6f8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03d7240c8190a64dcbc669772808 |
completed | March 9, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69af0183eb84819087d7184de28f5514 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:41 p.m.