Triple
T25063515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rdf:Bag |
E627723
|
entity |
| Predicate | membershipOrder |
P163822
|
FINISHED |
| Object | unordered |
—
|
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: unordered | Statement: [rdf:Bag, membershipOrder, unordered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: membershipOrder Context triple: [rdf:Bag, membershipOrder, unordered]
-
A.
membershipStructure
Indicates the organizational or hierarchical arrangement that defines how members are grouped, related, and governed within a collective or system.
-
B.
membershipStatus
Indicates the current state or level of an entity’s participation or affiliation within a group, organization, or program.
-
C.
membershipBy
Indicates that one entity holds membership or belongs to a group, organization, or collection defined by another entity.
-
D.
membershipConsistsOf
Indicates that a membership is composed of, or includes, specific member entities as its constituents.
-
E.
membershipPattern
Indicates a recurring or structured way in which an entity belongs to, participates in, or is included within a group, set, or organization.
- 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_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 18, 2026, 6:10 a.m.