Triple
T29489719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otsu Campus |
E748040
|
entity |
| Predicate | hasFacultyCommunity |
P181424
|
FINISHED |
| Object | Shiga University faculty |
—
|
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: Shiga University faculty | Statement: [Otsu Campus, hasFacultyCommunity, Shiga University faculty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFacultyCommunity Context triple: [Otsu Campus, hasFacultyCommunity, Shiga University faculty]
-
A.
hasFaculty
Indicates that an institution or department possesses or is associated with one or more faculty members.
-
B.
hasFacultyIn
Indicates that an institution or organization has faculty members associated with or working in a particular department, field, or academic unit.
-
C.
hasCampusCommunity
Indicates that an institution or location possesses an associated campus-based community or group of people connected to it.
-
D.
hasAcademicCommunity
Indicates that an entity is associated with, belongs to, or participates in a particular academic community or scholarly group.
-
E.
hasUniversityFaculty
Indicates that a university or academic institution employs or is associated with one or more faculty members.
- F. None of above. chosen
Provenance (4 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_69f0bd448c6881908aa6b475cefd5ddc |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69f77648979c8190b6cdbb835ab8987c |
completed | May 3, 2026, 4:22 p.m. |
Created at: April 28, 2026, 4:12 p.m.