Triple
T20158484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Journey That Wasn’t |
E491639
|
entity |
| Predicate | hasScreening |
P138887
|
FINISHED |
| Object | art museums |
—
|
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: art museums | Statement: [A Journey That Wasn’t, hasScreening, art museums]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScreening Context triple: [A Journey That Wasn’t, hasScreening, art museums]
-
A.
screenedWith
Indicates that one entity is examined, tested, or evaluated using another entity as the screening method, tool, or criterion.
-
B.
hasScreened
Indicates that one entity has shown, displayed, or evaluated another entity, typically in the context of presenting media or conducting a review or check.
-
C.
screenedBefore
Indicates that one entity was screened or shown at an earlier time than another entity.
-
D.
screenedIn
Indicates that one entity has been evaluated or assessed to determine whether it meets certain criteria for inclusion, participation, or further consideration in relation to another entity.
-
E.
wasScreenedAs
Indicates that an entity was evaluated or tested and classified as a particular role, status, or category during a screening process.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667e27aa88190a326288b992ea274 |
completed | April 20, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69e54cfd924881909b55f3e4d3e7e070 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc2bc3c819088c33cd263303433 |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 11:34 p.m.