Triple
T32256659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pegasus rocket family |
E824042
|
entity |
| Predicate | customerTypes |
P809
|
FINISHED |
| Object | civil space agencies |
—
|
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: civil space agencies | Statement: [Pegasus rocket family, customerTypes, civil space agencies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: customerTypes Context triple: [Pegasus rocket family, customerTypes, civil space agencies]
-
A.
customerType
chosen
Indicates the classification or category assigned to a customer based on their characteristics, status, or relationship with a business.
-
B.
customerGroup
Indicates a relationship in which an entity belongs to, is classified under, or is associated with a particular group of customers.
-
C.
customerValue
Indicates the degree of benefit, importance, or worth that a customer represents to a business or organization.
-
D.
issuerCustomerType
Indicates the type or category of customer associated with or defined by the issuer.
-
E.
underlyingCompanyCustomerType
Indicates the type or category of customer relationship that an underlying company has (e.g., retail, institutional, corporate).
- 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bc549ce88190963037034412e0b1 |
completed | May 3, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:41 a.m.