Triple
T26089007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domino |
E658064
|
entity |
| Predicate | frequentPartner |
P161677
|
FINISHED |
| Object | Cable |
—
|
NE NERFINISHED |
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: Cable | Statement: [Domino, frequentPartner, Cable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequentPartner Context triple: [Domino, frequentPartner, Cable]
-
A.
frequentPartner
chosen
Indicates that two entities regularly engage in a shared activity or interaction together more often than with others.
-
B.
frequentPatron
Indicates that one entity regularly and repeatedly visits, uses, or patronizes another entity (such as a place, service, or establishment).
-
C.
loyaltyProgramPartner
Indicates that there is a partnership or affiliation between entities within the same loyalty or rewards program.
-
D.
partnerInFlight
Indicates that two or more entities are collaborating or jointly participating in the same flight or air travel activity.
-
E.
associatedWithFrequentFlyerProgram
Indicates that an entity has a connection or involvement with a frequent flyer program, such as membership, participation, or affiliation.
- 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 26, 2026, 7:45 p.m.