Triple
T1800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Manchester |
E33
|
entity |
| Predicate | hasNotableResearchArea |
P3
|
FINISHED |
| Object | graphene research |
—
|
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: graphene research | Statement: [University of Manchester, hasNotableResearchArea, graphene research]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableResearchArea Context triple: [University of Manchester, hasNotableResearchArea, graphene research]
-
A.
hasAcademicStaff
Indicates that an institution or organization employs or is associated with one or more academic staff members.
-
B.
hasAcademicRank
Indicates that an entity holds a specific academic rank or title within an educational or research institution.
-
C.
hasFaculty
Indicates that an institution or department possesses or is associated with one or more faculty members.
-
D.
fieldOfWork
chosen
Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
-
E.
hasNotableFacility
Indicates that an entity possesses or hosts a facility that is of particular significance, prominence, or interest.
- 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_69a22a285828819081a58308fb963df1 |
completed | Feb. 27, 2026, 11:35 p.m. |
| NER | Named-entity recognition | batch_69a2346846608190b6b40d31f1dbd685 |
completed | Feb. 28, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69a233c396ec8190986608d07fb251d4 |
completed | Feb. 28, 2026, 12:16 a.m. |
Created at: Feb. 27, 2026, 11:36 p.m.