Triple
T25063540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rdf:Bag |
E627723
|
entity |
| Predicate | supportsMultipleMembership |
P129532
|
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: [rdf:Bag, supportsMultipleMembership, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMultipleMembership Context triple: [rdf:Bag, supportsMultipleMembership, true]
-
A.
multiMember
chosen
Indicates that an entity participates as a member in more than one group, collection, or organizational unit simultaneously.
-
B.
supportsMultiuser
Indicates that the subject is capable of handling or enabling simultaneous use by multiple users.
-
C.
supportsForeignMembers
Indicates that an entity provides assistance, resources, or favorable conditions specifically to members originating from other countries or external organizations.
-
D.
hasMemberAlsoIn
Indicates that an entity has at least one member who also belongs to another specified group or collection.
-
E.
supportsMultipleMatches
Indicates that the relationship or operation can involve or return more than one matching counterpart rather than being limited to a single match.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 18, 2026, 6:10 a.m.