Triple
T10100794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Handy Park |
E216192
|
entity |
| Predicate | typicalAdmission |
P92432
|
FINISHED |
| Object | free |
—
|
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: free | Statement: [Handy Park, typicalAdmission, free]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAdmission Context triple: [Handy Park, typicalAdmission, free]
-
A.
admissionType
Indicates the category or manner in which an entity (such as a person or case) is formally accepted or admitted into a system, institution, or process.
-
B.
standardAdmitted
Indicates that an entity has been formally accepted or approved according to an established standard or set of criteria.
-
C.
admittedTo
Indicates that one entity has been formally accepted, enrolled, or granted entry into another entity, such as an institution, program, or facility.
-
D.
mediumOfAdmission
Indicates the method or channel through which an entity is admitted, accepted, or granted entry (e.g., via exam, recommendation, application type).
-
E.
hasAdmission
Indicates that an entity possesses or is associated with a specific admission event, record, or status (such as being admitted to a place, program, or institution).
- 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_69ca83d039f08190b9d10363221c69fb |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd09878f88190bcfa2c81fb10e821 |
completed | April 2, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd5150ae98819086c4f822114b4e2c |
completed | April 1, 2026, 5:09 p.m. |
Created at: March 30, 2026, 9:02 p.m.