Triple
T4804705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faculty of Arts and Science |
E106919
|
entity |
| Predicate | hasAdministration |
P24644
|
FINISHED |
| Object | dean |
—
|
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: dean | Statement: [Faculty of Arts and Science, hasAdministration, dean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdministration Context triple: [Faculty of Arts and Science, hasAdministration, dean]
-
A.
hasManagement
chosen
Indicates that one entity exercises managerial authority or oversight over another entity.
-
B.
hasAdministrationSite
Indicates the specific location or site on or in a subject where a substance, treatment, or intervention is administered.
-
C.
administersFrom
Indicates that an action, service, or process is carried out or managed starting from a particular source, location, or authority.
-
D.
hasAdministrativeType
Indicates that an entity is associated with a specific category or level of administrative classification (such as type of jurisdiction or administrative unit).
-
E.
coversAdministration
Indicates that one entity is responsible for managing, overseeing, or handling the administrative aspects of another entity or activity.
- 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_69bd43f6a1e08190bf0a372bfc336ee5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1c43a48190a65e56b1624a2339 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:23 p.m.