Triple
T8629827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sursum Corda |
E204371
|
entity |
| Predicate | cordaMeaning |
P47490
|
FINISHED |
| Object | hearts |
—
|
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: hearts | Statement: [Sursum Corda, cordaMeaning, hearts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cordaMeaning Context triple: [Sursum Corda, cordaMeaning, hearts]
-
A.
chain
Indicates that one entity is linked or connected in sequence to another, typically as part of a series or chain of related elements or actions.
-
B.
CISMeaning
chosen
Indicates that one concept, term, or symbol conveys, expresses, or stands for a particular meaning or interpretation in a given context.
-
C.
centralFormulaMeaning
Indicates that one formula or expression represents the primary or core meaning within a larger logical, mathematical, or semantic structure.
-
D.
blockchain
Indicates that an entity is associated with, utilizes, or pertains to blockchain technology or distributed ledger systems.
-
E.
ribbonMeaning
Indicates that one entity symbolically represents, commemorates, or raises awareness for a cause, event, or concept through the use of a ribbon.
- 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_69ca834a4ea0819094970dceb9e389f3 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5730309081909a9a0256c9bf5f8f |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc455906f8819082edd79cb4a1cf28 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:27 p.m.