Triple
T36690838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shugart |
E905949
|
entity |
| Predicate | hasNotableCompanyNameDerivedFrom |
P64362
|
FINISHED |
| Object | Shugart Associates |
E907260
|
NE 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: Shugart Associates | Statement: [Shugart, hasNotableCompanyNameDerivedFrom, Shugart Associates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableCompanyNameDerivedFrom Context triple: [Shugart, hasNotableCompanyNameDerivedFrom, Shugart Associates]
-
A.
hasCompanyName
Indicates that an entity is associated with or identified by a specific company name.
-
B.
hasNotableCompany
Indicates that an entity is associated with or linked to a company that is considered notable or significant in some context.
-
C.
hasNotableSuccessorCompany
Indicates that an entity is followed by another company recognized as a particularly important or prominent successor.
-
D.
hasCompanyNamedAfter
chosen
Indicates that one entity has a company whose name is derived from or identical to the other entity.
-
E.
hasParentCompanyOrigin
Indicates that an entity’s parent company originates from, or was founded in, a specified location or jurisdiction.
- F. None of above.
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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a3821c5588190a2be9833b016b8c5 |
completed | June 23, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.