Triple
T12441605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heatherdown School |
E297283
|
entity |
| Predicate | feeStatus |
P104951
|
FINISHED |
| Object | fee-paying |
—
|
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: fee-paying | Statement: [Heatherdown School, feeStatus, fee-paying]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feeStatus Context triple: [Heatherdown School, feeStatus, fee-paying]
-
A.
feeTypeAuthorized
Indicates that a particular type of fee is permitted or approved for use in a given context or relationship.
-
B.
feeType
Indicates the specific category or classification of a fee associated with a transaction, service, or obligation.
-
C.
feePolicy
Indicates the rules or conditions that determine how fees are calculated, applied, or charged in a given context.
-
D.
fareStatus
Indicates the current condition or classification of a fare within a pricing or ticketing context (e.g., available, restricted, or expired).
-
E.
hasFinancialStatus
Indicates that an entity possesses or is characterized by a particular financial condition, standing, or level of economic well-being.
- 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_69d6ada166c48190b902972cd2408fa3 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94df948308190ace333230a4a3b38 |
completed | April 10, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69d94d391c548190996a8c698357f273 |
completed | April 10, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69d94df652cc8190a1d2d685fa87cf98 |
completed | April 10, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:55 p.m.