Triple
T1841742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Society of the Cincinnati |
E41190
|
entity |
| Predicate | hasMembershipClass |
P121
|
FINISHED |
| Object | hereditary member |
—
|
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: hereditary member | Statement: [Society of the Cincinnati, hasMembershipClass, hereditary member]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMembershipClass Context triple: [Society of the Cincinnati, hasMembershipClass, hereditary member]
-
A.
hasMembershipBase
Indicates that an entity possesses or is associated with a foundational group or set of members that form its membership base.
-
B.
hasMemberType
chosen
Indicates that an entity includes or is associated with members belonging to a specified type or category.
-
C.
hasMembers
Indicates that a group, organization, or collection includes certain entities as its members.
-
D.
hasMemberFrom
Indicates that a group, organization, or collection includes at least one member originating from or belonging to a specified source, place, or category.
-
E.
membershipIn
Indicates that an entity belongs to, is part of, or holds membership in a particular group, organization, or collection.
- 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_69a88647f9388190909bc36e795bdaec |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdb0d2c8190a67f584e67979fa3 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.