Triple
T866213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skull and Bones |
E18707
|
entity |
| Predicate | membershipRestriction |
P19438
|
FINISHED |
| Object | Yale College seniors |
—
|
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: Yale College seniors | Statement: [Skull and Bones, membershipRestriction, Yale College seniors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: membershipRestriction Context triple: [Skull and Bones, membershipRestriction, Yale College seniors]
-
A.
membershipRelationRestrictedTo
chosen
Indicates that a membership relationship between entities is limited or constrained to a specified subset, context, or condition.
-
B.
membershipRequired
Indicates that access to or use of something is conditional on being a member of a specified group or organization.
-
C.
membershipOpenTo
Indicates that joining or belonging to a group, organization, or category is permitted for the specified entities or audience.
-
D.
accessRestriction
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
-
E.
membershipIncluded
Indicates that one entity’s membership or inclusion is contained within, or granted as part of, another entity’s membership.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac7cb1888190a46c16b30256451b |
completed | March 1, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69a4aa87504481909618a6815948da6f |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.