Triple
T2641984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Academician |
E62888
|
entity |
| Predicate | membershipLevel |
P18012
|
FINISHED |
| Object | full member |
—
|
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: full member | Statement: [Royal Academician, membershipLevel, full member]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: membershipLevel Context triple: [Royal Academician, membershipLevel, full member]
-
A.
membershipLevelAbove
Indicates that one entity’s membership level is ranked higher or more privileged than another entity’s membership level.
-
B.
membershipStatus
chosen
Indicates the current state or level of an entity’s participation or affiliation within a group, organization, or program.
-
C.
membershipLevelBelow
Indicates that one entity’s membership level is ranked lower or less privileged than another entity’s membership level.
-
D.
membershipPeak
Indicates the time or period at which an entity’s membership in a group or organization reaches its highest level.
-
E.
membershipStructure
Indicates the organizational or hierarchical arrangement that defines how members are grouped, related, and governed within a collective 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_69ab4c3f2dcc819082df80f5e032f690 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abd8fdc0bc8190b7fd102b87ee50d1 |
completed | March 7, 2026, 7:51 a.m. |
| PD | Predicate disambiguation | batch_69abd812849881908f956845a80e0205 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.