Triple
T15536679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argentina Davis Cup team |
E370362
|
entity |
| Predicate | notableTieSurface |
P34471
|
FINISHED |
| Object | outdoor clay |
—
|
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: outdoor clay | Statement: [Argentina Davis Cup team, notableTieSurface, outdoor clay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTieSurface Context triple: [Argentina Davis Cup team, notableTieSurface, outdoor clay]
-
A.
notableTie
Indicates a significant connection or association between entities that is noteworthy or distinguished in some context.
-
B.
notableSurface
chosen
Indicates that one entity is a surface or exterior of particular significance or prominence in relation to another entity.
-
C.
typeOfTie
Indicates the specific kind or category of relationship or connection that exists between two entities.
-
D.
notableCover
Indicates that one entity is a particularly well-known or significant cover version or adaptation of another entity.
-
E.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0442f3c688190a599165e526af2ed |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:06 a.m.