Triple
T25729061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mountain View, Arkansas |
E645188
|
entity |
| Predicate | CourthouseSquareKnownFor |
P159195
|
FINISHED |
| Object | informal outdoor music jams |
—
|
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: informal outdoor music jams | Statement: [Mountain View, Arkansas, CourthouseSquareKnownFor, informal outdoor music jams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CourthouseSquareKnownFor Context triple: [Mountain View, Arkansas, CourthouseSquareKnownFor, informal outdoor music jams]
-
A.
hasCityHall
Indicates that a location or administrative area possesses or is served by a specific city hall building or institution.
-
B.
hasCourthouse
Indicates that a location or jurisdiction possesses or contains a courthouse.
-
C.
courthouseLocatedIn
Indicates that a courthouse is situated within or at a specific geographic or administrative location.
-
D.
hasFamousSquare
Indicates that a place possesses or contains a well-known public square associated with it.
-
E.
courthouseCompletedIn
Indicates the year or date when a courthouse building was finished and became structurally complete.
- 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_69e77e85254081908d79ee4e8715f283 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fcba52e4819097aa7db2e8f4333a |
completed | May 2, 2026, 1:31 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 21, 2026, 11:10 p.m.