Triple
T33034341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drucker School of Management |
E845262
|
entity |
| Predicate | namedForContributionIn |
P184407
|
FINISHED |
| Object | management theory |
—
|
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: management theory | Statement: [Drucker School of Management, namedForContributionIn, management theory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForContributionIn Context triple: [Drucker School of Management, namedForContributionIn, management theory]
-
A.
namedIn
Indicates that one entity is explicitly mentioned or referenced by name within another entity (such as a document, statement, or record).
-
B.
namedForAward
Indicates that an entity is named in honor of a particular award.
-
C.
contributesToNameOf
Indicates that one entity plays a role in forming, influencing, or helping to determine the name of another entity.
-
D.
hasContributionFrom
Indicates that something (such as a work, project, or outcome) is created, influenced, or supported in part by a specified contributor.
-
E.
namedTo
Indicates that one entity has been given or assigned a specific name referring to another entity.
- 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_69f34951348c8190b56746b0a7018182 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7b0e3917481908a394680d76743c3 |
completed | May 3, 2026, 8:32 p.m. |
Created at: May 1, 2026, 1:24 a.m.