Triple
T1497596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brooklyn Museum |
E29720
|
entity |
| Predicate | rankBySizeInUSArtMuseums |
P1174
|
FINISHED |
| Object | one of the largest |
—
|
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: one of the largest | Statement: [Brooklyn Museum, rankBySizeInUSArtMuseums, one of the largest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankBySizeInUSArtMuseums Context triple: [Brooklyn Museum, rankBySizeInUSArtMuseums, one of the largest]
-
A.
majorMuseum
Indicates that a museum holds significant importance or prominence, typically due to its size, collections, reputation, or cultural impact.
-
B.
isMostVisitedArtMuseumIn
Indicates that an art museum holds the highest number of visitors compared to all other art museums within a specified location or region.
-
C.
nationalMuseum
Indicates that an entity functions as a primary, officially recognized museum representing a nation at the national level.
-
D.
rankBySize
chosen
Indicates that entities are ordered or compared based on their size.
-
E.
museumAt
Indicates that an entity (such as an exhibit, artifact, or event) is located at or associated with a particular museum.
- 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_69a498dba1d8819093b46a3a8d2485f1 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6ef5ce88190a6b520525a6d42a3 |
completed | March 1, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69a4c48a8cf48190a6ebf8d44a608a06 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.