Triple
T12434543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stade Roland Garros |
E297110
|
entity |
| Predicate | courtColor |
P104905
|
FINISHED |
| Object | red 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: red clay | Statement: [Stade Roland Garros, courtColor, red clay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtColor Context triple: [Stade Roland Garros, courtColor, red clay]
-
A.
courtCode
Indicates the specific court or judicial body associated with a legal case, proceeding, or record.
-
B.
decisionCourt
Indicates that a particular court rendered the decision or judgment in a given legal case or proceeding.
-
C.
courtStyle
Indicates the manner or stylistic approach in which a court conducts its proceedings or presents its decisions.
-
D.
courtLanguage
Indicates the language officially used in legal proceedings or by a court.
-
E.
courtContext
Indicates the legal or judicial setting, circumstances, or framework within which a court-related action or relationship takes place.
- F. None of above. chosen
Provenance (4 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94df948308190ace333230a4a3b38 |
completed | April 10, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69d94d391c548190996a8c698357f273 |
completed | April 10, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69d94df652cc8190a1d2d685fa87cf98 |
completed | April 10, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:55 p.m.