Triple
T9800660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PULSE network |
E237827
|
entity |
| Predicate | isMajorNetworkIn |
P14730
|
FINISHED |
| Object | U.S. debit market |
—
|
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: U.S. debit market | Statement: [PULSE network, isMajorNetworkIn, U.S. debit market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorNetworkIn Context triple: [PULSE network, isMajorNetworkIn, U.S. debit market]
-
A.
isMajorProviderFor
Indicates that one entity serves as a primary or leading supplier or source of goods, services, or resources for another entity.
-
B.
isMajorCarrierOf
Indicates that one entity serves as the primary or principal transporter or conveyor of another entity (such as goods, signals, or passengers).
-
C.
isMajorHubInCountry
Indicates that a location functions as a primary or central hub within a specified country, typically in terms of transport, commerce, or connectivity.
-
D.
isMajor
chosen
Indicates that an entity holds primary or greater significance, importance, or rank relative to others in a given context.
-
E.
isMajorHubType
Indicates that an entity functions as a primary or central hub within a larger network or system.
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda62a11a88190880e0cce24923b14 |
completed | April 1, 2026, 11:11 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:29 p.m.