Triple
T28277166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nightlife |
E713031
|
entity |
| Predicate | hasDigitalAspect |
P8017
|
FINISHED |
| Object | event discovery apps |
—
|
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: event discovery apps | Statement: [Nightlife, hasDigitalAspect, event discovery apps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDigitalAspect Context triple: [Nightlife, hasDigitalAspect, event discovery apps]
-
A.
hasDigitalEncoding
Indicates that one entity is represented, stored, or expressed using a specific digital code or encoding scheme provided by another entity.
-
B.
hasDigitalFacade
Indicates that an entity possesses a digital interface or representation that serves as its outward-facing surface or presentation.
-
C.
hasDigitalAccess
Indicates that an entity has the ability or permission to use or access digital resources, services, or information.
-
D.
hasDigitalForm
chosen
Indicates that something exists or is available in a digital or electronic format.
-
E.
hasDigitalArchive
Indicates that an entity maintains or is associated with a collection of materials stored in a digital archive.
- 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_69efb52275788190ae5181ccebef18ce |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 27, 2026, 11:20 p.m.