Triple
T29422406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finnish presidential Independence Day receptions |
E746188
|
entity |
| Predicate | invitationOnly |
P128871
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Finnish presidential Independence Day receptions, invitationOnly, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invitationOnly Context triple: [Finnish presidential Independence Day receptions, invitationOnly, true]
-
A.
isInvitational
Indicates that one entity extends or offers an invitation to another entity.
-
B.
invitationAuthority
Indicates that one entity has the authority or permission to invite another entity (or others) to participate in an event, group, or activity.
-
C.
exclusiveTo
Indicates that something is restricted or limited to a specific entity, group, or context and not shared with others.
-
D.
isInvited
Indicates that one entity has extended an invitation to another entity to participate in or attend something.
-
E.
exclusive
chosen
Indicates that the relationship or action applies only to a specific entity or set of entities, excluding all others from sharing that same status or participation.
- 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a69d4c48190bf63a61547e9f465 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 3:06 p.m.