Triple
T26047675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mesoamerican ballgame |
E647878
|
entity |
| Predicate | hasCourtFeature |
P182
|
FINISHED |
| Object | sloping walls |
—
|
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: sloping walls | Statement: [Mesoamerican ballgame, hasCourtFeature, sloping walls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCourtFeature Context triple: [Mesoamerican ballgame, hasCourtFeature, sloping walls]
-
A.
hasCourts
Indicates that an entity possesses, contains, or is equipped with one or more courts (e.g., legal, sports, or judicial facilities).
-
B.
hasCourtInEach
Indicates that an entity possesses or maintains a court in every member of a specified set of locations or jurisdictions.
-
C.
hasTypeOfCourt
Indicates that an entity is associated with or classified by a specific type or category of court.
-
D.
hasTribunal
Indicates that an entity is associated with or subject to a specific tribunal, such as a court or adjudicative body, that has authority over its cases or matters.
-
E.
hasFeature
chosen
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
- 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_69e77e8d419481908004e6318d28aaab |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: April 22, 2026, 9:10 a.m.