Triple
T28258469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pabellón II |
E712514
|
entity |
| Predicate | housesDepartmentOf |
P1467
|
FINISHED |
| Object | Faculty of Exact and Natural Sciences |
—
|
NE NERFINISHED |
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: Faculty of Exact and Natural Sciences | Statement: [Pabellón II, housesDepartmentOf, Faculty of Exact and Natural Sciences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: housesDepartmentOf Context triple: [Pabellón II, housesDepartmentOf, Faculty of Exact and Natural Sciences]
-
A.
houseBranch
Indicates that a particular house is a branch, subsidiary, or local unit of a larger parent organization or main house.
-
B.
governmentOffices
Indicates that one entity is a government office or administrative agency associated with, located in, or serving the other entity.
-
C.
governmentBranch
Indicates that one entity functions as an official division or branch within the structure of a government.
-
D.
department
chosen
Indicates that one entity functions as an organizational unit or division within another, typically larger, entity.
-
E.
laterDepartment
Indicates that one department occurs or is considered after another in a defined ordering or sequence.
- 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_69efb5207eb08190827e4c34048030b1 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 11:09 p.m.