Triple
T25415991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melrose |
E636833
|
entity |
| Predicate | isPrimarilyCommercial |
P125948
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Melrose, isPrimarilyCommercial, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimarilyCommercial Context triple: [Melrose, isPrimarilyCommercial, true]
-
A.
isPrimaryCommercialAreaOf
Indicates that one area serves as the main center of commercial activity for another specified place or region.
-
B.
hasCommercialFunction
Indicates that an entity serves a commercial role or purpose, such as engaging in trade, sales, or other profit-oriented activities.
-
C.
isPrimarilyUsedAs
chosen
Indicates that one entity serves mainly or most commonly in the role, function, or purpose specified by the other entity.
-
D.
isCommercialCommunityFor
Indicates a relationship where one entity serves as the primary commercial hub or marketplace community for another entity (such as a product, brand, or user group).
-
E.
hasCommercialField
Indicates that one entity possesses or is associated with a commercial-related field, area, or domain in relation to another entity.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 21, 2026, 1:55 p.m.