Triple
T25054893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carmelite Order |
E627489
|
entity |
| Predicate | wearsScapular |
P271
|
FINISHED |
| Object | Brown Scapular |
—
|
NE NERFINISHED |
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: Brown Scapular | Statement: [Carmelite Order, wearsScapular, Brown Scapular]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wearsScapular Context triple: [Carmelite Order, wearsScapular, Brown Scapular]
-
A.
wears
chosen
Indicates that one entity is dressed in, or has on its body, a particular item such as clothing or accessories.
-
B.
hasShoulderButtons
Indicates that an object, typically a device or controller, includes buttons positioned on its shoulders or top side edges.
-
C.
oftenDepictedWearing
Indicates that an entity is frequently shown or represented as wearing a particular item or type of clothing in depictions or portrayals.
-
D.
wearsInsigniaAt
Indicates that an entity is wearing or displaying a particular insignia at a specified location or point in time.
-
E.
wearsArmorOf
Indicates that one entity is equipped with or dressed in the specific armor that belongs to or is associated with another entity.
- 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_69e2ff2c45f48190afa28369f1df6786 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f454a5472c81909604372f24db8d62 |
completed | May 1, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:09 a.m.