Triple
T15449320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mirjam Poterbin |
E370105
|
entity |
| Predicate | sportAssociatedThroughFamily |
P67409
|
FINISHED |
| Object | basketball |
—
|
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: basketball | Statement: [Mirjam Poterbin, sportAssociatedThroughFamily, basketball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportAssociatedThroughFamily Context triple: [Mirjam Poterbin, sportAssociatedThroughFamily, basketball]
-
A.
memberOfSportsFamily
Indicates that an entity belongs to a family or lineage known for involvement in sports or athletic activities.
-
B.
relatedSport
chosen
Indicates that there is an association or connection between an entity and a particular sport.
-
C.
associatedWithTeamSport
Indicates a relationship where an entity is connected to, involved in, or participates in a team-based sport.
-
D.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
E.
relationshipTypeWithSport
Indicates the specific type or nature of the relationship an entity has with a particular sport (e.g., participation, affiliation, or role).
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ef9334c81908541e231b43eb012 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:21 a.m.