Triple
T28179613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Side Presbyterians |
E715988
|
entity |
| Predicate | reunionTime |
P164100
|
FINISHED |
| Object | 1758 |
—
|
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: 1758 | Statement: [New Side Presbyterians, reunionTime, 1758]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reunionTime Context triple: [New Side Presbyterians, reunionTime, 1758]
-
A.
reunionWith
Indicates that two or more entities come back together after a period of separation or absence.
-
B.
reunionContext
Indicates the situational setting, circumstances, or background in which a reunion between entities takes place.
-
C.
reunionType
Indicates the specific kind or category of reunion event that relates the involved entities.
-
D.
reunitedIn
Indicates that entities who were previously separated have come together again at a specific time or place.
-
E.
marksReunionOf
Indicates that an event, action, or state brings previously separated or distant entities back together, signifying their reunion.
- 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f642816d1c8190a507dad7bb85dfa5 |
completed | May 2, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 10:18 p.m.