Triple
T37249688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judo at the 1964 Summer Olympics |
E923955
|
entity |
| Predicate | teamEventsIncluded |
P160643
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Judo at the 1964 Summer Olympics, teamEventsIncluded, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamEventsIncluded Context triple: [Judo at the 1964 Summer Olympics, teamEventsIncluded, no]
-
A.
isTeamEventIncluded
chosen
Indicates whether a particular team event is counted or considered as part of a specified set, schedule, or collection of events.
-
B.
includesEvents
Indicates that one entity contains or encompasses one or more events as part of its scope or composition.
-
C.
teamEventsSeparatedSince
Indicates that two or more team-related events have occurred with a temporal gap or separation since a specified reference point.
-
D.
multiEventsIncluded
Indicates that multiple distinct events are collectively contained within, or form part of, a larger event set or grouping.
-
E.
teamIncludes
Indicates that a particular team has a specified member or entity as part of its composition.
- 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_69f76eaabb4c819093b751b139dad551 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb4134225081909fd60703b8cae397 |
completed | May 6, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69fb35bf767081908de8345358ca7f44 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.