Triple
T7237705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clásico Capitalino |
E155271
|
entity |
| Predicate | matchIntensity |
P16069
|
FINISHED |
| Object | fiercely contested |
—
|
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: fiercely contested | Statement: [Clásico Capitalino, matchIntensity, fiercely contested]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchIntensity Context triple: [Clásico Capitalino, matchIntensity, fiercely contested]
-
A.
matchType
Indicates the specific category or nature of how two or more entities correspond or align with each other within a given context.
-
B.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
C.
isIntense
chosen
Indicates that something exhibits a high degree of strength, force, or concentration in its quality, effect, or activity.
-
D.
intensityScale
Indicates the degree or level of strength, magnitude, or severity associated with an event, property, or measurement, typically according to a defined scale.
-
E.
typicalMatchType
Indicates the usual or most common type of match or pairing that characterizes how two entities are related or aligned.
- 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_69c688143bfc81908d4176617735e601 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea552a688190a00f5d0ad982f787 |
completed | March 27, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69c6e7644648819096a5e2de5d0dbe97 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:55 p.m.