Triple
T22928189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedarian Order |
E569366
|
entity |
| Predicate | hasOriginalMission |
P111900
|
FINISHED |
| Object | ransoming Christian captives from Muslim territories |
—
|
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: ransoming Christian captives from Muslim territories | Statement: [Mercedarian Order, hasOriginalMission, ransoming Christian captives from Muslim territories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalMission Context triple: [Mercedarian Order, hasOriginalMission, ransoming Christian captives from Muslim territories]
-
A.
hadMission
Indicates that an entity (such as a person, organization, or vehicle) was assigned or carried out a specific mission or operation.
-
B.
hasCoreMission
chosen
Indicates that an entity possesses a primary, central mission or fundamental purpose that defines its main focus or reason for existence.
-
C.
originalMissionStatus
Indicates the initial state or condition of a mission at the time it was first defined or launched.
-
D.
hasNotableMission
Indicates that an entity is associated with a mission or undertaking that is considered significant or noteworthy.
-
E.
hasNamesakeMission
Indicates that one entity has a mission named after it or sharing its name.
- 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_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. |
Created at: April 17, 2026, 3:43 p.m.