Triple
T21120379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Island Gold Coast estates |
E520411
|
entity |
| Predicate | manyNowUsedAs |
P142925
|
FINISHED |
| Object | museums |
—
|
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: museums | Statement: [Long Island Gold Coast estates, manyNowUsedAs, museums]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: manyNowUsedAs Context triple: [Long Island Gold Coast estates, manyNowUsedAs, museums]
-
A.
historicallyUsedFor
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
B.
oftenUsedAsNameFor
Indicates that something frequently serves as a name or designation for another entity.
-
C.
usedToBe
Indicates that something held a particular state, role, or property in the past but no longer does in the present.
-
D.
usedInPastFor
Indicates that one entity was previously utilized for another entity or purpose in the past.
-
E.
isFamouslyUsedIn
Indicates that something is widely recognized or well-known for being used in a particular context, work, or situation.
- 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_69e0b50a623881909c0bbaf4f2c055e7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72233a43481909535560514d388be |
completed | April 21, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69e5dbff56848190a03b350a9305c612 |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2e03d88819086f8b641656ad8b0 |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 2:55 p.m.