Triple
T5195825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian Science literature |
E117267
|
entity |
| Predicate | continuedDevelopment |
P13185
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Christian Science literature, continuedDevelopment, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuedDevelopment Context triple: [Christian Science literature, continuedDevelopment, 20th century]
-
A.
development
Indicates a process or relationship in which something grows, advances, or becomes more complex or mature over time.
-
B.
laterDevelopments
chosen
Indicates that subsequent events, changes, or outcomes occurred following an earlier situation or state.
-
C.
developmentLinkedTo
Indicates that the development or progression of one entity is causally or contextually connected to the development or progression of another entity.
-
D.
plannedDevelopment
Indicates that one entity has been designated or scheduled for future development or construction by another entity.
-
E.
developmentStart
Indicates the point in time or event when the development process of something begins.
- 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_69bd4462ed04819084fcb01eb9d2fa74 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7adb034c819086bf8a85fbf158f4 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77b9a67c8190819612257ea746b4 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:46 p.m.