Triple
T31456729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | neo-Friesian school |
E802470
|
entity |
| Predicate | revivesWorkOf |
P101361
|
FINISHED |
| Object | Jakob Friedrich Fries |
—
|
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: Jakob Friedrich Fries | Statement: [neo-Friesian school, revivesWorkOf, Jakob Friedrich Fries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revivesWorkOf Context triple: [neo-Friesian school, revivesWorkOf, Jakob Friedrich Fries]
-
A.
revivedBy
Indicates that an entity has been brought back to life, consciousness, or active state through the action or intervention of another entity.
-
B.
comebackWorkFor
Indicates that an entity returns to a previous workplace or employer to work again.
-
C.
reconstructionWorkBy
Indicates that a reconstruction project or effort is carried out, overseen, or authored by a specific agent or entity.
-
D.
isRevitalizationOf
chosen
Indicates that one entity is a renewed, restored, or modernized version of another, bringing it back into active or improved condition.
-
E.
revivedAs
Indicates that an entity, after having ceased to exist or function in its original form, comes back into existence or operation in a new or restored form.
- 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_69f348c678ac81908a2e950867619061 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 9:16 p.m.