Triple
T25063479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ContainerMembershipProperty |
E627722
|
entity |
| Predicate | hasMemberPropertyExample |
P163670
|
FINISHED |
| Object | rdf:_3 |
—
|
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:_3 | Statement: [ContainerMembershipProperty, hasMemberPropertyExample, rdf:_3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberPropertyExample Context triple: [ContainerMembershipProperty, hasMemberPropertyExample, rdf:_3]
-
A.
hasMemberPropertyExample
chosen
Indicates that a member of a group or collection possesses a specific property illustrated by an example.
-
B.
haveProperty
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
-
C.
hasMemberType
Indicates that an entity includes or is associated with members belonging to a specified type or category.
-
D.
hasMembershipBy
Indicates that an entity holds or acquires membership in a group, organization, or program by means of a specified agent, process, or instrument.
-
E.
hasMemberWithIdentity
Indicates that a group or collection includes at least one member that possesses a specified identity or identifier.
- 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_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 18, 2026, 6:10 a.m.