Triple
T28380009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tritton |
E718865
|
entity |
| Predicate | fieldOfNotableAssociation |
P1481
|
FINISHED |
| Object | engineering |
—
|
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: engineering | Statement: [Tritton, fieldOfNotableAssociation, engineering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldOfNotableAssociation Context triple: [Tritton, fieldOfNotableAssociation, engineering]
-
A.
notablyAssociatedWith
chosen
Indicates that one entity is prominently or distinctively connected with another in a way that is especially noteworthy or remarkable.
-
B.
hasNearbyNotablePersonAssociation
Indicates a relationship where an entity is associated with a notable person who is located nearby or in close geographic proximity.
-
C.
namedPersonAssociation
Indicates a relationship where one entity is associated with or identified by a specific personal name.
-
D.
hasNotablePersonConnection
Indicates that there exists a significant or noteworthy personal, professional, or historical relationship between the subject and the referenced person.
-
E.
notoriouslyAssociatedWith
Indicates a widely recognized and often negative or infamous association between one entity and another.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 28, 2026, 1:05 a.m.