Triple
T16102611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal School (Honolulu) |
E390658
|
entity |
| Predicate | studentBoarding |
P16557
|
FINISHED |
| Object | 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: boarding | Statement: [Royal School (Honolulu), studentBoarding, boarding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studentBoarding Context triple: [Royal School (Honolulu), studentBoarding, boarding]
-
A.
boardingStudents
Indicates that certain students reside at and are accommodated by an educational institution, typically living on campus rather than commuting.
-
B.
studentComponent
Indicates that one entity functions as a student-related part, module, or subunit within a larger system, structure, or context.
-
C.
studentsWing
Indicates a relationship where a particular wing, section, or area is designated for or associated with students.
-
D.
hasBoardingStudents
chosen
Indicates that an educational institution accommodates students who reside on campus as boarders.
-
E.
schoolBoard
Indicates that an entity serves as or is governed by a school board responsible for overseeing educational policies and administration.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff6976ec8190b499e99b196b0285 |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.