Triple
T8108711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burbn |
E189289
|
entity |
| Predicate | targetUserActivity |
P80501
|
FINISHED |
| Object | sharing photos of places visited |
—
|
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: sharing photos of places visited | Statement: [Burbn, targetUserActivity, sharing photos of places visited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetUserActivity Context triple: [Burbn, targetUserActivity, sharing photos of places visited]
-
A.
targetedActivity
Indicates that an activity is specifically directed or focused toward a particular entity, group, or objective.
-
B.
targetsUseCase
Indicates that one entity is aimed at or designed to address a particular use case associated with another entity.
-
C.
activityTime
Indicates the time period during which an activity occurs or is scheduled to take place.
-
D.
targetUserPosition
Indicates the spatial position or location of a specified user relative to a reference frame or environment.
-
E.
peakActivity
Indicates that an entity is at its highest or most intense level of activity within a given period or context.
- 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_69ca82b9d5848190a24672775d5c5011 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb42fa40e08190955fccec1a28eb34 |
completed | March 31, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69cb04a2ed1c8190b73562321ad688bc |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14be17208190bb51c3dfcb613f20 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:32 p.m.