Triple
T6441206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maagdenhuis |
E138227
|
entity |
| Predicate | hasRectorOffice |
P29283
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Maagdenhuis, hasRectorOffice, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRectorOffice Context triple: [Maagdenhuis, hasRectorOffice, yes]
-
A.
hasRectorate
Indicates that an institution or organization possesses or is governed by a rectorate (a rector’s administrative office or governing body).
-
B.
hasProperOffice
Indicates that an entity maintains an officially designated, appropriate office or place of business.
-
C.
hasOffice
Indicates that an entity possesses or maintains an office at a particular location or within a specific organization.
-
D.
hasAssociatedOffice
Indicates that an entity is linked to or connected with a particular office in an official or functional capacity.
-
E.
hasRectorateBuilding
chosen
Indicates that an institution possesses or is associated with a specific building that houses its rectorate (central administrative leadership).
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06968c6a88190a623da9bd3152a66 |
completed | March 22, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69c060f96980819091bab9335922a457 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:46 p.m.