Triple
T6466443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Jesus Generation |
E142243
|
entity |
| Predicate | describesMovement |
P70961
|
FINISHED |
| Object | Jesus movement in the United States |
—
|
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: Jesus movement in the United States | Statement: [The Jesus Generation, describesMovement, Jesus movement in the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesMovement Context triple: [The Jesus Generation, describesMovement, Jesus movement in the United States]
-
A.
movementDepicted
Indicates that some form of motion or change in position is visually represented or illustrated.
-
B.
refersToPersonMovement
Indicates that one entity is referencing, describing, or otherwise relating to the physical movement or relocation of a person.
-
C.
movementCharacteristic
Indicates how an entity moves or behaves in motion, such as its style, pattern, or quality of movement.
-
D.
usesMovement
Indicates that an entity performs or involves some form of movement as part of its action or behavior.
-
E.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
- F. None of above. chosen
Provenance (4 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_69c008d3bf4c8190bcf798c5ba9d6fb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06a1159ec81909bbfa9a9d6fa1616 |
completed | March 22, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69c0673d46a08190bc8bcd29f9555fe7 |
completed | March 22, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69c067da970481908a038995ba7dfb4b |
completed | March 22, 2026, 10:06 p.m. |
Created at: March 22, 2026, 4:49 p.m.