Triple
T19960828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NS Flex |
E479807
|
entity |
| Predicate | billingEntity |
P138037
|
FINISHED |
| Object | NS Flex invoice |
—
|
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: NS Flex invoice | Statement: [NS Flex, billingEntity, NS Flex invoice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: billingEntity Context triple: [NS Flex, billingEntity, NS Flex invoice]
-
A.
billing
Indicates that one entity charges another entity for goods or services, typically by issuing an invoice or request for payment.
-
B.
billedBy
Indicates that one entity issues a bill or invoice to another entity for goods, services, or charges.
-
C.
billingAuthorityType
Indicates the specific role or category of authority responsible for issuing or managing a bill in the relationship between the parties.
-
D.
billCharacteristic
Indicates that a bill possesses or is associated with a particular characteristic or attribute.
-
E.
billingMethod
Indicates the way in which payment is arranged, processed, or charged for a product, service, or account.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65af4520c81909986a47289ba801e |
completed | April 20, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:54 p.m.