Triple
T34770101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marianne Engblom |
E1002339
|
entity |
| Predicate | roleInEngblomVCarey |
P203017
|
FINISHED |
| Object | plaintiff |
—
|
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: plaintiff | Statement: [Marianne Engblom, roleInEngblomVCarey, plaintiff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInEngblomVCarey Context triple: [Marianne Engblom, roleInEngblomVCarey, plaintiff]
-
A.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
-
B.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
C.
roleAtVicariousVisions
Indicates the specific position or role an entity holds at Vicarious Visions.
-
D.
designedRole
Indicates that one entity has been created, configured, or intended to serve a particular function, purpose, or role in relation to another entity.
-
E.
roleInEngine
Indicates the specific function or responsibility an entity has within an engine or engine-like system.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a00dc330b148190aaae2ac6a5327960 |
completed | May 10, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_6a00d9d2904881909dafbfe7b9e5ad81 |
completed | May 10, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_6a00dc3268248190a723e1b7b29f9cda |
completed | May 10, 2026, 7:27 p.m. |
Created at: May 3, 2026, 3:59 p.m.