Triple
T36371567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Men In Love |
E895768
|
entity |
| Predicate | containsFictionalCommentator |
P196082
|
FINISHED |
| Object | various invented critics |
—
|
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: various invented critics | Statement: [Old Men In Love, containsFictionalCommentator, various invented critics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsFictionalCommentator Context triple: [Old Men In Love, containsFictionalCommentator, various invented critics]
-
A.
hasFictionalSpeaker
chosen
Indicates that a work, text, or expression is presented as being spoken by an invented or non-real speaker rather than an actual person.
-
B.
coCommentatorWith
Indicates that two individuals serve together as commentators on the same event, program, or broadcast.
-
C.
hasFictionalSpokesperson
Indicates that an entity is represented or promoted by a spokesperson who is a fictional or imaginary character.
-
D.
hasCommentaryOn
Indicates that one entity provides commentary, explanation, or evaluative remarks about another entity.
-
E.
hasCommentaryIn
Indicates that an entity is discussed, analyzed, or annotated within a specific commentary work or source.
- 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_69f76e5115588190ad8738860b7bc68b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a01295195748190b896d99c3d1f6134 |
completed | May 11, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_6a0128fe96dc8190a73715ab08752dd1 |
completed | May 11, 2026, 12:55 a.m. |
Created at: May 3, 2026, 4:10 p.m.