Triple
T36610789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Natalie von Bertouch |
E903458
|
entity |
| Predicate | playedForState |
P26504
|
FINISHED |
| Object | South Australia |
—
|
NE NERFINISHED |
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: South Australia | Statement: [Natalie von Bertouch, playedForState, South Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedForState Context triple: [Natalie von Bertouch, playedForState, South Australia]
-
A.
playedInState
chosen
Indicates that an entity (typically a person or team) participated in games or competitions within a specified state.
-
B.
playedFor
Indicates that one entity has been a member of or participated as a player for a particular team, organization, or group.
-
C.
playedForStart
Indicates the time or date when an entity (typically a person) began playing for a particular team or organization.
-
D.
laterPlayedFor
Indicates that an individual was a member of or played for a team or organization at a time after a previously referenced team or organization.
-
E.
teamPlayedFor
Indicates that a person was a member of and played for a particular sports team.
- 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_69f76e6960e4819092047756ceb9a17e |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: May 3, 2026, 4:11 p.m.