Triple
T37723096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Partners & Napier |
E939642
|
entity |
| Predicate | projectInvolvement |
P74692
|
FINISHED |
| Object | Parrish Art Museum |
—
|
NE NERFINISHED |
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: Parrish Art Museum | Statement: [Partners & Napier, projectInvolvement, Parrish Art Museum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectInvolvement Context triple: [Partners & Napier, projectInvolvement, Parrish Art Museum]
-
A.
collaborativeProjects
Indicates that two or more entities work together on shared projects or initiatives toward common goals.
-
B.
projectsOn
Indicates that one entity casts, directs, or extends itself onto the surface, area, or domain of another entity.
-
C.
projectsBetween
Indicates a relationship where something is projected or extends from one entity to another across an intervening space or set of entities.
-
D.
hasBeenInvolvedIn
chosen
Indicates that an entity has participated in, taken part in, or been connected to a particular event, activity, or situation.
-
E.
isOnProject
Indicates that an entity is currently assigned to, involved with, or working on a particular project.
- 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:18 p.m.