Triple
T8378459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OPC |
E197632
|
entity |
| Predicate | customerGroup |
P82393
|
FINISHED |
| Object | mariners |
—
|
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: mariners | Statement: [OPC, customerGroup, mariners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: customerGroup Context triple: [OPC, customerGroup, mariners]
-
A.
customerType
Indicates the classification or category assigned to a customer based on their characteristics, status, or relationship with a business.
-
B.
exportCustomer
Indicates initiating the transfer or output of customer-related data from one system or context to another, typically for integration, backup, or reporting purposes.
-
C.
customerValue
Indicates the degree of benefit, importance, or worth that a customer represents to a business or organization.
-
D.
participantGroup
Indicates a relationship in which a set or group of entities jointly participate in a common event, activity, or interaction.
-
E.
majorCustomer
Indicates that one entity is a primary or high-value customer of another entity, typically contributing a significant portion of business or revenue.
- 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_69ca82f64c188190af4e1608036b865d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80c229708190b813f5e7e44e10d4 |
completed | March 31, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69cb70cfe82881909fe374ba52649e84 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d823b08190a54fadb50660cda5 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 6:02 p.m.