Triple
T3279173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darren Lockyer |
E68831
|
entity |
| Predicate | testAppearances |
P47670
|
FINISHED |
| Object | 59 for Australia |
—
|
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: 59 for Australia | Statement: [Darren Lockyer, testAppearances, 59 for Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testAppearances Context triple: [Darren Lockyer, testAppearances, 59 for Australia]
-
A.
appearsFor
Indicates that one entity is presented, shown, or made visible on behalf of, or in representation of, another entity.
-
B.
appearedWith
Indicates that two entities were present or participated together in the same context, event, or medium.
-
C.
appearsAs
Indicates that one entity is presented, perceived, or manifested in the form, role, or guise of another entity.
-
D.
allegedAppearanceType
Indicates the type or nature of an appearance that is claimed or reported to have occurred, without confirming that the appearance actually took place.
-
E.
laterAppearancesIn
Indicates that one entity makes additional or subsequent appearances in relation to another entity after an initial occurrence.
- 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_69ad859c463481909ca4be267336c290 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0155430819097c806ee407dc1e4 |
completed | March 8, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69ada420167c81909b6e2702db296d9e |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada526764881908e4bd52938d5374d |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:10 p.m.