Triple
T13656561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Cod Baseball League |
E326874
|
entity |
| Predicate | usesHostFamilies |
P111018
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cape Cod Baseball League, usesHostFamilies, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHostFamilies Context triple: [Cape Cod Baseball League, usesHostFamilies, true]
-
A.
hasSiblingHosts
Indicates that two or more entities share at least one common host, making them sibling hosts in relation to that shared hosting entity.
-
B.
networkFamily
Indicates a relationship where entities belong to the same network grouping or family, typically sharing common infrastructure, protocols, or organizational affiliation.
-
C.
allowsForFamily
Indicates that one entity enables or makes it possible for another entity to support or include family-related participation, benefits, or involvement.
-
D.
hasHostFather
Indicates a relationship where one person serves as the host father of another, typically in a hosting or exchange context.
-
E.
containsFamily
Indicates that one entity includes or encompasses members of a particular family group within it.
- F. None of above. chosen
Provenance (4 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc61d56e4819084ae3c16ecdf4a05 |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:52 p.m.