Triple
T8020888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mothers |
E186737
|
entity |
| Predicate | typicalIssuer |
P80606
|
FINISHED |
| Object | technology startups |
—
|
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 startups | Statement: [Mothers, typicalIssuer, technology startups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalIssuer Context triple: [Mothers, typicalIssuer, technology startups]
-
A.
issuerType
Indicates the classification or category of the entity that issues something (such as a document, credential, or instrument).
-
B.
issuedBy
Indicates that something (such as a document, order, or statement) has been formally created, authorized, or released by a particular agent or authority.
-
C.
hasIssuerPrimaryBusiness
Indicates that an entity’s main or primary line of business is identified or characterized by the associated business activity or classification.
-
D.
issuerProduces
Indicates that an issuer creates, generates, or brings into existence a particular product, document, asset, or item.
-
E.
targetIssuerProfile
Indicates a relationship where a specific profile is designated as the primary or intended issuer in a given context.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3e8d90488190b57d1e748e272061 |
completed | March 31, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bcbbc0819094a98e7ffffb7a40 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:20 p.m.