Triple
T22928216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedarian Order |
E569366
|
entity |
| Predicate | hasTypeOfHabit |
P150292
|
FINISHED |
| Object | white habit with scapular and shield of the order |
—
|
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: white habit with scapular and shield of the order | Statement: [Mercedarian Order, hasTypeOfHabit, white habit with scapular and shield of the order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfHabit Context triple: [Mercedarian Order, hasTypeOfHabit, white habit with scapular and shield of the order]
-
A.
hasHabit
Indicates that an entity regularly performs, practices, or exhibits a particular behavior or routine.
-
B.
habitNumber
Indicates a numerical designation or identifier assigned to a particular habit within a set or sequence of habits.
-
C.
hasActivityType
Indicates the specific kind or category of activity associated with an entity or event.
-
D.
habitIncludes
Indicates that a particular habit encompasses, involves, or is composed of a specified activity, behavior, or element.
-
E.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
- F. None of above. chosen
Provenance (4 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_69e2458f7d008190901dccbaebeaba24 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f180db6db88190bc8efb691dcdfdba |
completed | April 29, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:43 p.m.