Triple
T32723431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Davis Cup team |
E836736
|
entity |
| Predicate | surfaceTypesUsed |
P1242
|
FINISHED |
| Object | hard court |
—
|
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: hard court | Statement: [United States Davis Cup team, surfaceTypesUsed, hard court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceTypesUsed Context triple: [United States Davis Cup team, surfaceTypesUsed, hard court]
-
A.
surfaceType
chosen
Indicates the kind or classification of surface associated with an entity or interaction.
-
B.
surfaceTypeAround
Indicates the type or nature of the surface that surrounds or is immediately adjacent to a given entity.
-
C.
surfaceBehavior
Indicates how an entity behaves or interacts specifically at or on its surface.
-
D.
replacedSurfaceType
Indicates that one surface type has been substituted or changed to another surface type.
-
E.
surfaceFeatureOf
Indicates that one entity is a surface-level characteristic, pattern, or feature belonging to or present on another entity.
- 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_69f34935455881909088975d79460418 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:11 a.m.