Triple
T13870155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French Rite |
E333426
|
entity |
| Predicate | hasCoreSymbolism |
P34702
|
FINISHED |
| Object | square and compasses |
—
|
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: square and compasses | Statement: [French Rite, hasCoreSymbolism, square and compasses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreSymbolism Context triple: [French Rite, hasCoreSymbolism, square and compasses]
-
A.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
-
B.
shapeSymbolism
Indicates how a particular shape is associated with or conveys symbolic meaning within a given context.
-
C.
emblemSymbolism
chosen
Indicates that one entity serves as an emblem whose design or features symbolically represent or convey meanings about another entity.
-
D.
incorporatesSymbolismFrom
Indicates that one entity includes or integrates symbolic elements, motifs, or meanings derived from another entity.
-
E.
hasCulturalCore
Indicates that one entity embodies or provides the central cultural values, practices, or identity that fundamentally define 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_69d81c5ced9c8190b0e9bcc6effe5959 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a101488190bd790b28033d38b9 |
completed | April 14, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69de05972f3881909977b4c843984f88 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:14 p.m.