Triple
T32267260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isabelle/ZF |
E824318
|
entity |
| Predicate | maintainedWith |
P183139
|
FINISHED |
| Object | Isabelle distribution |
—
|
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: Isabelle distribution | Statement: [Isabelle/ZF, maintainedWith, Isabelle distribution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainedWith Context triple: [Isabelle/ZF, maintainedWith, Isabelle distribution]
-
A.
maintainedAs
Indicates that one entity is kept in a particular state, condition, or configuration by another entity through ongoing care, management, or support.
-
B.
legacyMaintainedBy
Indicates that responsibility for preserving, continuing, or upholding a legacy rests with a particular entity.
-
C.
maintainedFor
Indicates that something is kept in a particular state, condition, or operation for the benefit, use, or purpose of another entity.
-
D.
oftenMaintainedBy
Indicates that something is regularly or frequently kept in working order, cared for, or updated by a particular agent or entity.
-
E.
stillMaintained
Indicates that the subject continues to be actively maintained or supported over time.
- 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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f798387ea481909f51303f53a22e52 |
completed | May 3, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79798663481908d6bc48dd6a94ca6 |
completed | May 3, 2026, 6:44 p.m. |
Created at: May 1, 2026, 12:42 a.m.