Triple
T36388303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sverre Anker Ousdal |
E896257
|
entity |
| Predicate | hasWorkedSince |
P44456
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Sverre Anker Ousdal, hasWorkedSince, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkedSince Context triple: [Sverre Anker Ousdal, hasWorkedSince, 1960s]
-
A.
hasWorkedFor
Indicates that an entity has been employed by or has provided work or services to another entity.
-
B.
hasWorkedIn
Indicates that a person has been employed or has performed work within a particular organization, location, or domain for some period of time.
-
C.
hasWorkUsedFor
Indicates that a particular work (e.g., document, resource, or artifact) is utilized for a specific purpose, task, or activity.
-
D.
hasWorkRecordedBy
Indicates that a particular work (such as a composition or piece) has been captured or documented in an audio or video recording made by a specified recorder or performer.
-
E.
hasWorkPeriod
chosen
Indicates that an entity is associated with a specific span of time during which it performs or is engaged in some work or activity.
- 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69febce5877c8190a5e000ef5331ec88 |
completed | May 9, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_69febad1cd588190abc7686bcb39a371 |
completed | May 9, 2026, 4:40 a.m. |
Created at: May 3, 2026, 4:10 p.m.