Triple
T27963518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollos |
E704651
|
entity |
| Predicate | helpedBelieversIn |
P129918
|
FINISHED |
| Object | Achaia |
—
|
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: Achaia | Statement: [Apollos, helpedBelieversIn, Achaia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpedBelieversIn Context triple: [Apollos, helpedBelieversIn, Achaia]
-
A.
instructsBelieversTo
Indicates that a subject gives commands, guidance, or directives specifically to believers to perform or refrain from certain actions.
-
B.
helpedCause
Indicates that one entity contributed to bringing about, enabling, or facilitating an outcome or event involving another entity.
-
C.
reactionOfBelievers
Indicates how believers respond or behave in reaction to a particular event, message, or situation.
-
D.
beliefEncouragedBy
Indicates that one entity’s belief is supported, strengthened, or promoted as a result of influence, actions, or encouragement from another entity.
-
E.
helpsIn
chosen
Indicates that one entity provides assistance, support, or aid to another entity in performing or achieving a particular task, activity, or goal.
- 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 7:33 p.m.