Triple
T1312906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gordonstoun School |
E28033
|
entity |
| Predicate | boardingType |
P18241
|
FINISHED |
| Object | full boarding |
—
|
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: full boarding | Statement: [Gordonstoun School, boardingType, full boarding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boardingType Context triple: [Gordonstoun School, boardingType, full boarding]
-
A.
boarding
Indicates that one entity is getting onto or entering a vehicle, vessel, or similar conveyance associated with another entity.
-
B.
boardingProcess
Indicates the process or sequence of actions by which passengers move from a waiting area onto a vehicle (such as an airplane, train, or bus).
-
C.
boardingGroups
Indicates that certain entities are assigned to or associated with specific boarding groups for an ordered boarding process.
-
D.
hasBoardingType
chosen
Indicates the specific manner or method by which an entity is boarded or accessed (e.g., how passengers or items are taken on).
-
E.
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.
- 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_69a498532c3481909223b74af2e578df |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1572b1c8190ab978198c2d655c8 |
completed | March 1, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69a4beebcb348190964bd7215811942c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.