Triple
T20292737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missionary Training Centers |
E510064
|
entity |
| Predicate | startTimePoint |
P66434
|
FINISHED |
| Object | before missionaries enter assigned mission field |
—
|
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: before missionaries enter assigned mission field | Statement: [Missionary Training Centers, startTimePoint, before missionaries enter assigned mission field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimePoint Context triple: [Missionary Training Centers, startTimePoint, before missionaries enter assigned mission field]
-
A.
startPoint
Indicates the initial location or position from which an object, path, or action begins.
-
B.
positionStartTime
chosen
Indicates the time at which a position, role, or placement begins.
-
C.
startTimeDepicted
Indicates that the subject visually represents the starting time of an event, process, or state.
-
D.
startTimeNote
Indicates the specific time-related note or annotation associated with when an event or action begins.
-
E.
startTimeAsCardinal
Indicates the specific clock time at which an event or action begins, expressed as a cardinal (numeric) value rather than a textual or formatted time.
- 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_69e0b4c652388190b782cad965e5a098 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e677024de08190bfa54ae26b5486d1 |
completed | April 20, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:12 a.m.