Triple
T25999026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fen-Edebiyat Fakültesi |
E646567
|
entity |
| Predicate | bulunduğuÜniversiteKampüsü |
P36352
|
FINISHED |
| Object | İstanbul Teknik Üniversitesi kampüsleri |
—
|
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: İstanbul Teknik Üniversitesi kampüsleri | Statement: [Fen-Edebiyat Fakültesi, bulunduğuÜniversiteKampüsü, İstanbul Teknik Üniversitesi kampüsleri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bulunduğuÜniversiteKampüsü Context triple: [Fen-Edebiyat Fakültesi, bulunduğuÜniversiteKampüsü, İstanbul Teknik Üniversitesi kampüsleri]
-
A.
isPartOfCampus
chosen
Indicates that one place, facility, or area is located within and belongs to a larger campus.
-
B.
campus
Indicates that an entity is located on, associated with, or taking place within a particular campus.
-
C.
campus1
Indicates a relationship where an entity is identified as a campus or is located on/associated with a particular campus.
-
D.
universityLocatedIn
Indicates that a university is situated within or associated with a specific geographic location or administrative region.
-
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_69e77e88cb8481908da31d4a00661f55 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605720be48190b1b64ecdccfaec17 |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 8:58 a.m.