Triple
T38010096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jarvis Lorry |
E948340
|
entity |
| Predicate | relationshipToDrManette |
P207551
|
FINISHED |
| Object | longtime friend |
—
|
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: longtime friend | Statement: [Jarvis Lorry, relationshipToDrManette, longtime friend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToDrManette Context triple: [Jarvis Lorry, relationshipToDrManette, longtime friend]
-
A.
relationshipToManni
Indicates a relational connection that an entity has specifically with Manni, such as their role, association, or familial/ social tie to Manni.
-
B.
relationshipTypeWithMarvin
Indicates the specific nature or category of the relationship an entity has with Marvin.
-
C.
relationshipToDrLeoMarvin
Indicates the specific personal or professional connection an entity has with Dr. Leo Marvin.
-
D.
relationshipToPlotDevice
Indicates how an entity is functionally or narratively connected to a specific plot device within a story.
-
E.
relationshipToMannyMachado
Indicates the specific type of relationship or connection an entity has to Manny Machado.
- 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_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037df009f4819082e04683e6e8a106 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:20 p.m.