Triple
T14040675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yankee Conference (with William & Mary) |
E337835
|
entity |
| Predicate | memberOfFCS |
P10
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Yankee Conference (with William & Mary), memberOfFCS, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberOfFCS Context triple: [Yankee Conference (with William & Mary), memberOfFCS, yes]
-
A.
memberOfGroupWith
Indicates that an entity belongs to, or is associated as a member with, a particular group or collection of entities.
-
B.
memberOf
chosen
Indicates that an entity belongs to, is part of, or is a constituent of a larger group, organization, or collection.
-
C.
membershipIn
Indicates that an entity belongs to, is part of, or holds membership in a particular group, organization, or collection.
-
D.
membershipConsistsOf
Indicates that a membership is composed of, or includes, specific member entities as its constituents.
-
E.
confersMembershipIn
Indicates that one entity grants or bestows membership status in a group, organization, or category upon 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de311814e48190adb637e1c97c0658 |
completed | April 14, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.