Triple
T6252585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emanuel R. Piore |
E140082
|
entity |
| Predicate | notableEmployerSector |
P50235
|
FINISHED |
| Object | technology industry |
—
|
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: technology industry | Statement: [Emanuel R. Piore, notableEmployerSector, technology industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEmployerSector Context triple: [Emanuel R. Piore, notableEmployerSector, technology industry]
-
A.
notableSector
chosen
Indicates that an entity is particularly prominent, influential, or significant within a specified sector or industry.
-
B.
notableEmployer
Indicates that an entity has been employed by, or has worked for, a particularly significant or noteworthy organization or individual.
-
C.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
D.
notableIndustry
Indicates that an entity is significantly recognized or prominent within a specified industry or sector.
-
E.
notableBusinessType
Indicates that an entity is notably associated with, characterized by, or best known for a particular type of business.
- 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_69c008b4858c819095b0199114a9a87b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063417c8c8190945049881819d307 |
completed | March 22, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c05605566c81908e197f5accd072d2 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:24 p.m.