Triple
T14498949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central University of Venezuela |
E359579
|
entity |
| Predicate | campusDesignStyle |
P27120
|
FINISHED |
| Object | modernist architecture |
—
|
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: modernist architecture | Statement: [Central University of Venezuela, campusDesignStyle, modernist architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campusDesignStyle Context triple: [Central University of Venezuela, campusDesignStyle, modernist architecture]
-
A.
campusDesign
chosen
Indicates the relationship between an educational institution and the overall planning, layout, and architectural design of its campus environment.
-
B.
campusDesignation
Indicates the formal classification or status assigned to a particular campus within an institution or system.
-
C.
campusArchitect
Indicates that one entity serves as the architect responsible for designing or planning the campus associated with the other entity.
-
D.
campusType
Indicates the classification or category of a campus based on its type (e.g., main, satellite, urban, rural).
-
E.
cityCampus
Indicates that a campus is located within or associated with a particular city.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9311cc748190880c784f173b7f2b |
completed | April 14, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:21 a.m.