Triple
T9435583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louis Armstrong Stadium |
E227495
|
entity |
| Predicate | hasCourtCount |
P4502
|
FINISHED |
| Object | 1 main match 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: 1 main match court | Statement: [Louis Armstrong Stadium, hasCourtCount, 1 main match court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCourtCount Context triple: [Louis Armstrong Stadium, hasCourtCount, 1 main match court]
-
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.
numberOfCourts
chosen
Indicates the quantity of courts associated with or present at a given entity or location.
-
D.
hasNumberOfCourtsOfLastResort
Indicates the quantity of highest-level judicial courts (courts of last resort) that an entity possesses or is associated with.
-
E.
hasStateCourt
Indicates that a given jurisdiction or region possesses an official court that operates at the state level.
- 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_69ca8437a7ac81908651de48f2d2141d |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7e64109081908222f590928bc572 |
completed | April 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:50 p.m.