Triple
T24844618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Servants of Relief for Incurable Cancer |
E621710
|
entity |
| Predicate | habitSymbol |
P18980
|
FINISHED |
| Object | Dominican rosary |
—
|
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: Dominican rosary | Statement: [Servants of Relief for Incurable Cancer, habitSymbol, Dominican rosary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: habitSymbol Context triple: [Servants of Relief for Incurable Cancer, habitSymbol, Dominican rosary]
-
A.
habitIncludes
Indicates that a particular habit encompasses, involves, or is composed of a specified activity, behavior, or element.
-
B.
habitNumber
Indicates a numerical designation or identifier assigned to a particular habit within a set or sequence of habits.
-
C.
typicalSymbol
chosen
Indicates that something serves as a characteristic or commonly recognized symbol representing something else.
-
D.
hasHabit
Indicates that an entity regularly performs, practices, or exhibits a particular behavior or routine.
-
E.
hatCharakter
Indicates that an entity possesses or exhibits a particular character, trait, or quality.
- 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_69e2fac185d48190a0a6073ad1f6b792 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:19 a.m.