Triple
T29934123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persepolis–Esteghlal |
E760308
|
entity |
| Predicate | derbyParticipants |
P33356
|
FINISHED |
| Object | Persepolis FC |
—
|
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: Persepolis FC | Statement: [Persepolis–Esteghlal, derbyParticipants, Persepolis FC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derbyParticipants Context triple: [Persepolis–Esteghlal, derbyParticipants, Persepolis FC]
-
A.
hasParticipantCity
Indicates that a city is involved as a participant in an event, activity, or relationship.
-
B.
finalTournamentParticipants
Indicates that the specified entities are the participants who qualified for and compete in the final round of a tournament.
-
C.
numberOfParticipants
Indicates the total count of entities involved in a particular event, activity, or relationship.
-
D.
eventParticipant
chosen
Indicates that an entity takes part in, is involved in, or participates in a particular event.
-
E.
hasParticipants
Indicates that an event, activity, or situation involves one or more entities as participants in it.
- 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_69f224631674819080c8d089674f9f4f |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f677d346e4819089c1c7231d9df64e |
completed | May 2, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:19 p.m.