Triple
T37517803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ecumenical councils |
E932680
|
entity |
| Predicate | continueIn |
P111156
|
FINISHED |
| Object | modern era |
—
|
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: modern era | Statement: [Ecumenical councils, continueIn, modern era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continueIn Context triple: [Ecumenical councils, continueIn, modern era]
-
A.
continuedThrough
Indicates that an event, state, or process persisted without interruption across or beyond a specified point, period, or boundary.
-
B.
intendedToContinue
Indicates that an entity had the plan or purpose to persist in a particular state, activity, or relationship beyond a given point in time.
-
C.
continuesFor
Indicates that an event, state, or process persists or remains in effect for a specified duration or period.
-
D.
continuedInRegion
chosen
Indicates that an event, process, or state persisted or carried on within a specified geographic or spatial region.
-
E.
continuedBy
Indicates that one entity carries on, extends, or resumes the activity, process, or sequence initiated by 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: May 3, 2026, 4:17 p.m.