Triple
T27545030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malaysia Cup |
E695336
|
entity |
| Predicate | historicalParticipant |
P66992
|
FINISHED |
| Object | Singapore |
—
|
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: Singapore | Statement: [Malaysia Cup, historicalParticipant, Singapore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalParticipant Context triple: [Malaysia Cup, historicalParticipant, Singapore]
-
A.
historicalMember
Indicates that an entity was formerly a member of another entity or group during a past period, but is not necessarily a current member.
-
B.
historicalEventParticipation
chosen
Indicates that an entity took part in, contributed to, or was involved in a specific historical event.
-
C.
historicallyAttendedBy
Indicates that an entity has been attended by another entity at some point in the past, rather than in the present.
-
D.
notableParticipant
Indicates that an entity plays a significant or distinguished role as a participant in an event, activity, or context.
-
E.
partOfHistoricalPeople
Indicates that one entity is a subset, member, or component of a larger group or collection of historical people.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: April 27, 2026, 1:32 p.m.