Triple
T25019089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goliad, Texas |
E626522
|
entity |
| Predicate | courthouseStyle |
P71383
|
FINISHED |
| Object | Classical Revival |
—
|
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: Classical Revival | Statement: [Goliad, Texas, courthouseStyle, Classical Revival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courthouseStyle Context triple: [Goliad, Texas, courthouseStyle, Classical Revival]
-
A.
courtStyle
Indicates the manner or stylistic approach in which a court conducts its proceedings or presents its decisions.
-
B.
courtDesignStyle
chosen
Indicates the stylistic design or aesthetic approach applied to a court or courtroom.
-
C.
courtroom
Indicates a relationship where a legal proceeding or judicial action takes place within or is associated with a specific courtroom.
-
D.
hasCourthouse
Indicates that a location or jurisdiction possesses or contains a courthouse.
-
E.
traditionalCourt
Indicates that an entity is associated with or takes place in a conventional or historically established court of law, as opposed to a modern, alternative, or informal judicial setting.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:06 a.m.