Triple
T25063512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rdf:Bag |
E627723
|
entity |
| Predicate | membershipIndicatedBy |
P162857
|
FINISHED |
| Object | rdf:_n |
—
|
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: rdf:_n | Statement: [rdf:Bag, membershipIndicatedBy, rdf:_n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: membershipIndicatedBy Context triple: [rdf:Bag, membershipIndicatedBy, rdf:_n]
-
A.
membershipBy
Indicates that one entity holds membership or belongs to a group, organization, or collection defined by another entity.
-
B.
membershipRecordedBy
Indicates that the recording or documentation of a membership was carried out or created by a specific agent or system.
-
C.
membershipStatus
Indicates the current state or level of an entity’s participation or affiliation within a group, organization, or program.
-
D.
membershipIn
Indicates that an entity belongs to, is part of, or holds membership in a particular group, organization, or collection.
-
E.
membershipBased
Indicates that access, participation, or inclusion in something is conditional on holding a membership or belonging to a defined group.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f62e83045c8190a424a2e401a88e9e |
completed | May 2, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62d886828819080ec2f742b9449e3 |
completed | May 2, 2026, 4:59 p.m. |
Created at: April 18, 2026, 6:10 a.m.