Triple
T11845310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appellate Division Courthouse of New York State |
E281758
|
entity |
| Predicate | hasSculpturalProgram |
P101821
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Appellate Division Courthouse of New York State, hasSculpturalProgram, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSculpturalProgram Context triple: [Appellate Division Courthouse of New York State, hasSculpturalProgram, yes]
-
A.
hasSculptor
Indicates that one entity serves as the sculptor (creator of a sculpture) of another entity.
-
B.
sculpturalProgramDirectedBy
Indicates that the overall design and execution of a sculptural program is overseen, guided, or managed by a specific director or authority.
-
C.
sculpturalProgramDesignedBy
Indicates that a sculptural program was conceived, planned, or created by a particular designer or artist.
-
D.
hasArtProgram
Indicates that an entity offers or participates in an art-related educational or creative program.
-
E.
hasSculptureType
Indicates that an entity is associated with a sculpture and specifies the type or category of that sculpture.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a65b5ff08190bb58361f6a6acdca |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:43 p.m.