Triple
T22259462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brittany Forgler |
E550178
|
entity |
| Predicate | startsActivity |
P28445
|
FINISHED |
| Object | running |
—
|
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: running | Statement: [Brittany Forgler, startsActivity, running]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startsActivity Context triple: [Brittany Forgler, startsActivity, running]
-
A.
activityStartContext
Indicates the circumstances, conditions, or situation present at the moment an activity begins.
-
B.
exportActivity
Indicates an action where goods, services, or data are sent out from one entity or region to another for trade or distribution across borders.
-
C.
startedActingOn
chosen
Indicates that one entity has begun to perform, execute, or apply an action, influence, or process upon another entity.
-
D.
activityStartApprox
Indicates that the start time of an activity is known only approximately, rather than as an exact timestamp.
-
E.
laterActivity
Indicates that one activity occurs after another in time, establishing a temporal ordering 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_69e11e42adb8819087714772ea606709 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f138c5b54c8190854690ba599639fa |
completed | April 28, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69e72fe1e0cc8190bd13cff2a0846225 |
completed | April 21, 2026, 8:05 a.m. |
Created at: April 16, 2026, 8:39 p.m.