Triple
T28992457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Penn Charter School |
E736061
|
entity |
| Predicate | foundingCharterType |
P19150
|
FINISHED |
| Object | proprietary charter |
—
|
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: proprietary charter | Statement: [William Penn Charter School, foundingCharterType, proprietary charter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundingCharterType Context triple: [William Penn Charter School, foundingCharterType, proprietary charter]
-
A.
charterType
chosen
Indicates the specific category or kind of charter under which an entity, agreement, or operation is formally established or governed.
-
B.
foundedByCharterFrom
Indicates that an entity was formally established through an official charter issued by another entity.
-
C.
grantedCharter
Indicates that an authority formally issued an official charter or authorization to an entity.
-
D.
governedByCharterFrom
Indicates that an entity operates under the authority, rules, or framework established by a specific charter issued by another entity.
-
E.
charterDefines
Indicates that a charter specifies or establishes the rules, roles, or scope governing something.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 28, 2026, 9:27 a.m.