Triple
T25063513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rdf:Bag |
E627723
|
entity |
| Predicate | membershipPropertyType |
P138319
|
FINISHED |
| Object | rdf:Property |
—
|
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:Property | Statement: [rdf:Bag, membershipPropertyType, rdf:Property]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: membershipPropertyType Context triple: [rdf:Bag, membershipPropertyType, rdf:Property]
-
A.
membershipPropertiesAreSubPropertyOf
Indicates that the membership properties in question are defined as subproperties of another, more general property in the relationship.
-
B.
clubMembershipType
Indicates the specific category or level of membership that an entity holds within a club.
-
C.
membershipCharacteristic
Indicates that an entity possesses a specific attribute or quality by virtue of its membership in a particular group or category.
-
D.
membershipStructure
Indicates the organizational or hierarchical arrangement that defines how members are grouped, related, and governed within a collective or system.
-
E.
propertiesType
chosen
Indicates that one entity is classified as a specific type or category of properties associated with another entity.
- 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_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 18, 2026, 6:10 a.m.