Triple
T28683251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venturing |
E726061
|
entity |
| Predicate | allowsMembershipFrom |
P95320
|
FINISHED |
| Object | completion of eighth grade |
—
|
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: completion of eighth grade | Statement: [Venturing, allowsMembershipFrom, completion of eighth grade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsMembershipFrom Context triple: [Venturing, allowsMembershipFrom, completion of eighth grade]
-
A.
allowsAffiliationOf
Indicates that one entity grants permission or enables another entity to establish or hold an affiliation with it.
-
B.
confersMembershipIn
Indicates that one entity grants or bestows membership status in a group, organization, or category upon another entity.
-
C.
admitsFrom
chosen
Indicates that one entity accepts or enrolls individuals coming from another specified source or institution.
-
D.
canIncludeNonMembersFor
Indicates that something is allowed to include or involve entities that are not members in relation to a specified target or context.
-
E.
compulsoryMembershipFrom
Indicates that one entity is required or mandated to hold membership in 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_69f01d867608819086bc3e6b4f9de866 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 28, 2026, 5:10 a.m.