Triple
T1084036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trevi Fountain |
E24010
|
entity |
| Predicate | associatedBelief |
P9182
|
FINISHED |
| Object | coin toss ensures return to Rome |
—
|
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: coin toss ensures return to Rome | Statement: [Trevi Fountain, associatedBelief, coin toss ensures return to Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedBelief Context triple: [Trevi Fountain, associatedBelief, coin toss ensures return to Rome]
-
A.
believedBy
chosen
Indicates that a particular proposition, statement, or entity is held to be true or accepted as real by a specified believer.
-
B.
sharesBelief
Indicates that two or more entities hold the same belief or conviction.
-
C.
associatedHeir
Indicates that one entity is designated or recognized as the heir connected to, or inheriting from, another entity.
-
D.
associatedWithDecision
Indicates a relationship where an entity is linked or connected to a particular decision, such that the decision is relevant to, influenced by, or otherwise tied to that entity.
-
E.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
- 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9608bac819085196cc0f8fbb2e7 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73f4310819086281f8ec67d1a32 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.