Triple
T14131351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burgundy |
E350173
|
entity |
| Predicate | memberEntitlement |
P112930
|
FINISHED |
| Object | Access to program-specific perks |
—
|
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: Access to program-specific perks | Statement: [Burgundy, memberEntitlement, Access to program-specific perks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberEntitlement Context triple: [Burgundy, memberEntitlement, Access to program-specific perks]
-
A.
membershipIncluded
Indicates that one entity’s membership or inclusion is contained within, or granted as part of, another entity’s membership.
-
B.
membershipConsistsOf
Indicates that a membership is composed of, or includes, specific member entities as its constituents.
-
C.
membershipStatus
Indicates the current state or level of an entity’s participation or affiliation within a group, organization, or program.
-
D.
membershipBy
Indicates that one entity holds membership or belongs to a group, organization, or collection defined by another entity.
-
E.
eligibleMembers
Indicates that certain entities meet the required criteria or conditions to be considered eligible members of a specified group or category.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de610aa434819096671c5aabb9134a |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 11:03 p.m.