Triple
T20638917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missionaries (Whitman College mascot) |
E507165
|
entity |
| Predicate | replacedDueTo |
P56544
|
FINISHED |
| Object | cultural concerns |
—
|
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: cultural concerns | Statement: [Missionaries (Whitman College mascot), replacedDueTo, cultural concerns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedDueTo Context triple: [Missionaries (Whitman College mascot), replacedDueTo, cultural concerns]
-
A.
replacedBecause
chosen
Indicates that one entity has been substituted for another specifically due to a particular reason or cause.
-
B.
replacedDuring
Indicates that one entity took the place of another entity during a specified time period or interval.
-
C.
replacedWith
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
D.
renamedDueTo
Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
-
E.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by 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_69e0b4be702c8190a3d2410a881d310a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6ad1163008190aa9df36750a952d2 |
completed | April 20, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69e5a0155bd48190b3c769a12cc2c83d |
completed | April 20, 2026, 3:40 a.m. |
Created at: April 16, 2026, 11:42 a.m.