Triple
T37639314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Bishoprics |
E936570
|
entity |
| Predicate | presentDayDepartmentIncludes |
P195115
|
FINISHED |
| Object | Moselle |
—
|
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: Moselle | Statement: [Three Bishoprics, presentDayDepartmentIncludes, Moselle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentDayDepartmentIncludes Context triple: [Three Bishoprics, presentDayDepartmentIncludes, Moselle]
-
A.
presentDayDepartment
Indicates that an entity is currently administered or located within a specific modern-day department (administrative division).
-
B.
basedInDepartment
Indicates that an entity operates or has its primary affiliation within a specific department.
-
C.
worksInDepartment
Indicates that an entity is employed in and performs their job duties within a particular department.
-
D.
presentDayIncludes
Indicates that the current day in a given calendar or time context encompasses or contains a specified time, date, or event.
-
E.
mayIncludeDepartment
Indicates that one entity is allowed or able to contain or encompass a particular department as part of its structure or composition.
- 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_69f76ed31d8881908405da6c6d2f0463 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
| PDg | Predicate description generation | batch_69fda4fe67a08190bdaa84ceabd6de6c |
completed | May 8, 2026, 8:55 a.m. |
Created at: May 3, 2026, 4:18 p.m.