Triple
T5296689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mormon pioneers |
E119873
|
entity |
| Predicate | facedChallenge |
P2189
|
FINISHED |
| Object | harsh winter conditions |
—
|
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: harsh winter conditions | Statement: [Mormon pioneers, facedChallenge, harsh winter conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facedChallenge Context triple: [Mormon pioneers, facedChallenge, harsh winter conditions]
-
A.
challengeUndertaken
Indicates that an entity has accepted and is actively engaging in a specific challenge or demanding task.
-
B.
hasChallenge
chosen
Indicates that an entity faces, experiences, or is confronted with a particular difficulty, obstacle, or problem.
-
C.
hasBeenChallengedIn
Indicates that an entity has faced a challenge, contest, or dispute within a specified context, domain, or setting.
-
D.
mayBeChallengedBy
Indicates that one entity is allowed or able to be opposed, questioned, or contested by another entity.
-
E.
challengedPractice
Indicates that one entity has questioned, disputed, or formally opposed the validity, appropriateness, or continuation of another entity’s practice or procedure.
- 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_69bd446f22b88190b6a47fb91c68a3e7 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8e44e7c881909b241b2fec366038 |
completed | March 20, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69bd845097ac81909678624c4907fda4 |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:53 p.m.