Triple
T25797048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake of the Cross |
E649713
|
entity |
| Predicate | hasNameBasedOn |
P140404
|
FINISHED |
| Object | religious symbolism |
—
|
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: religious symbolism | Statement: [Lake of the Cross, hasNameBasedOn, religious symbolism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameBasedOn Context triple: [Lake of the Cross, hasNameBasedOn, religious symbolism]
-
A.
hasGivenNameBasis
Indicates that one entity’s given name is derived from, based on, or formed using another entity (such as a name, word, or person) as its basis.
-
B.
basedOnName
chosen
Indicates that one entity is derived, determined, or identified using the name of another entity.
-
C.
basedOnElementName
Indicates that one entity is derived from, determined by, or otherwise depends on the name of another element.
-
D.
hasNameDayBaseName
Indicates that an entity’s name day is based on or associated with a particular base name.
-
E.
hasBaseNameMeaning
Indicates that an entity’s base name carries or is associated with a particular meaning.
- 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 22, 2026, 6:31 a.m.