Triple
T9846132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chris Marker |
E239345
|
entity |
| Predicate | workedOnTheme |
P56598
|
FINISHED |
| Object | memory |
—
|
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: memory | Statement: [Chris Marker, workedOnTheme, memory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workedOnTheme Context triple: [Chris Marker, workedOnTheme, memory]
-
A.
associatedWithWorkTheme
chosen
Indicates a relationship where something is connected or related to a particular work theme or subject matter.
-
B.
workedUnder
Indicates that one entity was hierarchically subordinate to and performed work under the supervision or authority of another entity.
-
C.
workOn
Indicates that an agent is actively engaged in performing tasks or making progress on a particular project, object, or assignment.
-
D.
workedOnCharacter
Indicates that an entity contributed effort or labor to developing, portraying, or otherwise engaging with a particular character.
-
E.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
- 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_69ca84e3f0c48190ada72a65ebd50efd |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb36156308190b26892702f3b41e0 |
completed | April 2, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69cd03e57cac8190914bb5ae608a6e0e |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:34 p.m.