Triple
T16356674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Wilderness Downtown |
E397198
|
entity |
| Predicate | isPersonalized |
P86594
|
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: [The Wilderness Downtown, isPersonalized, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPersonalized Context triple: [The Wilderness Downtown, isPersonalized, true]
-
A.
isPersonalGiftOf
Indicates that one entity is a gift personally given by another entity, typically reflecting a direct, individual act of giving.
-
B.
isPersonalTo
chosen
Indicates that something is uniquely associated with, belonging to, or intended for a specific individual, rather than being general or shared.
-
C.
supportsPersonalization
Indicates that one entity enables or provides functionality for tailoring content, behavior, or experience to the preferences or characteristics of another entity.
-
D.
customizableBy
Indicates that one entity can be modified, configured, or tailored in some way by another entity.
-
E.
personalGiftOf
Indicates that one entity has personally given another entity a gift, emphasizing a direct, individual act of gifting between them.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2facf67e0819089a23ce6f5642fbe |
completed | April 18, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.