Triple
T11927592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Francois Louw |
E283822
|
entity |
| Predicate | hasPlayedAtLevel |
P39395
|
FINISHED |
| Object | international |
—
|
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: international | Statement: [Francois Louw, hasPlayedAtLevel, international]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayedAtLevel Context triple: [Francois Louw, hasPlayedAtLevel, international]
-
A.
playedAtLevel
chosen
Indicates that an entity participated or performed in an activity, event, or game at a specified level of difficulty, competition, or hierarchy.
-
B.
wasPlayed
Indicates that an entity (such as a game, song, or media item) was performed, executed, or used by someone or something.
-
C.
hasReturnedToPlayIn
Indicates that an entity has resumed participating or performing in a particular event, context, or location after a period of absence.
-
D.
playedAfter
Indicates that one event, performance, or action occurred later in time than another.
-
E.
hasScoredFor
Indicates that one entity has scored points, goals, or similar achievements on behalf of another entity, such as a team, organization, or side.
- 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903024afc8190a97aa3263dc7d017 |
completed | April 10, 2026, 2:02 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3af0188190bfb22be5c97b3349 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.