Triple
T23900352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Os Três Grandes |
E601023
|
entity |
| Predicate | hasNotableDerby |
P113569
|
FINISHED |
| Object | Benfica vs Sporting CP |
—
|
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: Benfica vs Sporting CP | Statement: [Os Três Grandes, hasNotableDerby, Benfica vs Sporting CP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableDerby Context triple: [Os Três Grandes, hasNotableDerby, Benfica vs Sporting CP]
-
A.
notableDerbyHosted
Indicates that an entity has hosted a derby event considered notable or significant.
-
B.
hasDerbyName
Indicates that an entity is known by or uses a specific derby name, typically as an alternate or performance-related identity.
-
C.
isDerby
chosen
Indicates that a competition or match is a derby, typically involving teams or participants from the same locality or with a strong rivalry.
-
D.
hasDerbyStatus
Indicates that an entity holds a specific status or classification related to a derby event or competition.
-
E.
hasNotableRace
Indicates that an entity is associated with a race or competition that is considered notable or significant.
- 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cdddca088190b6c26df984a143ad |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:26 p.m.