Triple
T5665790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Frisian |
E124852
|
entity |
| Predicate | successorLanguage |
P78
|
FINISHED |
| Object | Middle Frisian |
—
|
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: Middle Frisian | Statement: [Old Frisian, successorLanguage, Middle Frisian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorLanguage Context triple: [Old Frisian, successorLanguage, Middle Frisian]
-
A.
implementationLanguageOfSuccessor
Indicates that one entity is the implementation language used for the successor or follow-up version of another entity.
-
B.
successorLabel
Indicates that one entity is the direct successor or next in sequence to another entity, often inheriting its role, position, or label.
-
C.
hasSuccessorLanguageInRegion
Indicates that one language is followed or replaced by another language within a specific geographic region.
-
D.
successor
chosen
Indicates that one entity directly follows another in an ordered sequence or position.
-
E.
successorInGermanService
Indicates that one entity directly follows another in holding a particular role, position, or function within a German service or institution.
- 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_69c00828906881908966f270b8f130cf |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0236d3f94819095111c41a323612d |
completed | March 22, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_69c021ba4ec481909db8cdbf0e907dd6 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:43 p.m.