Triple
T4437256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RBA |
E95680
|
entity |
| Predicate | membershipBodyType |
P52477
|
FINISHED |
| Object | art society |
—
|
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: art society | Statement: [RBA, membershipBodyType, art society]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: membershipBodyType Context triple: [RBA, membershipBodyType, art society]
-
A.
typeOfMembershipBody
chosen
Indicates the specific kind or category of membership that an entity holds within a body or organization.
-
B.
parentBodyType
Indicates that one entity has a body type that serves as the parent or base classification from which another entity's body type is derived or organized.
-
C.
establishedBodyType
Indicates that an entity has formally created, founded, or set up a particular organizational body or structure.
-
D.
religiousBodyType
Indicates the type or classification of a religious organization or body to which an entity is related.
-
E.
residesOverBodyType
Indicates that one entity is positioned or located above another entity that is characterized by a specific body type.
- 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_69b3453ea2b48190a26f154b3b8fece5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3558b1d4481909060ede5e0ded4bc |
completed | March 13, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69b34f6078cc8190831b89f404198cc5 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:31 p.m.