Triple
T38218811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USM Auriga |
E1010753
|
entity |
| Predicate | scienceDivisionHead |
P68030
|
FINISHED |
| Object | Dr. Wren |
—
|
NE NERFINISHED |
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: Dr. Wren | Statement: [USM Auriga, scienceDivisionHead, Dr. Wren]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scienceDivisionHead Context triple: [USM Auriga, scienceDivisionHead, Dr. Wren]
-
A.
chiefScientist
Indicates that one entity serves as the primary or lead scientist for another entity, typically holding top scientific authority or responsibility.
-
B.
musicDepartmentHead
Indicates that one entity serves as the head or leader of the music department of another entity.
-
C.
soundDepartmentHead
Indicates that one entity serves as the head or chief person in charge of the sound department for the other entity (such as a film, show, or production).
-
D.
overseesDivision
chosen
Indicates that one entity has managerial or supervisory responsibility over a specific division of an organization.
-
E.
academicHead
Indicates that one entity serves as the chief academic leader or head of another entity, such as a department, program, or institution.
- 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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.