Triple
T19131733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beyond Foundationalism |
E468330
|
entity |
| Predicate | positionedWithin |
P41662
|
FINISHED |
| Object | postconservative evangelical theology |
—
|
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: postconservative evangelical theology | Statement: [Beyond Foundationalism, positionedWithin, postconservative evangelical theology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionedWithin Context triple: [Beyond Foundationalism, positionedWithin, postconservative evangelical theology]
-
A.
positionIncluded
chosen
Indicates that one position or spatial region is entirely contained within another position or spatial region.
-
B.
isPositionedAs
Indicates that one entity is placed or arranged in a specific spatial or conceptual position relative to another.
-
C.
coordinatesWithin
Indicates that one set of coordinates lies entirely inside the spatial bounds defined by another.
-
D.
positionInRange
Indicates that an entity’s position lies within a specified numerical or spatial range.
-
E.
positionedRelativeTo
Indicates that one entity’s spatial location is defined or described in relation to the position of another entity.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3e980288190859026c0a0873fe2 |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.