Triple
T30505535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Frum movement |
E776258
|
entity |
| Predicate | emergedBeforeEvent |
P56217
|
FINISHED |
| Object | Second World War |
—
|
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: Second World War | Statement: [John Frum movement, emergedBeforeEvent, Second World War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emergedBeforeEvent Context triple: [John Frum movement, emergedBeforeEvent, Second World War]
-
A.
existedBeforeEvent
chosen
Indicates that the subject entity was already in existence prior to the occurrence of the specified event.
-
B.
emergedWith
Indicates that one entity came forth, appeared, or became visible at the same time and in association with another entity.
-
C.
heirBeforeEvent
Indicates that one entity is designated as the heir of another prior to a specified event occurring.
-
D.
heldBefore
Indicates that one entity possessed or maintained control of something at an earlier time than another entity or event.
-
E.
cameIntoForceBefore
Indicates that one legal instrument, rule, or agreement became legally effective earlier in time than another.
- 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_69f2249a155c8190b1d512106007e9bb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f687b35f908190923e211cb3955135 |
completed | May 2, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:15 p.m.