Triple
T37618453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titus Abrasax |
E935995
|
entity |
| Predicate | relationshipToJupiterJones |
P206009
|
FINISHED |
| Object | attempted husband |
—
|
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: attempted husband | Statement: [Titus Abrasax, relationshipToJupiterJones, attempted husband]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToJupiterJones Context triple: [Titus Abrasax, relationshipToJupiterJones, attempted husband]
-
A.
relationToJupiter
Indicates a spatial or conceptual relationship that an entity has with the planet Jupiter, such as position, distance, or association relative to it.
-
B.
relationshipToJoni
Indicates the specific familial, social, or professional connection that one entity has to the person or entity named Joni.
-
C.
relationshipToJoeCinque
Indicates a specified type of relationship or connection that an entity has to Joe Cinque.
-
D.
relationshipTypeWithJesse
Indicates the specific type or nature of the relationship that an entity has with Jesse.
-
E.
relationshipToJack
Indicates the specific type of personal or social connection an entity has with Jack.
- 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_69f76ed16b748190ad6add183b1be688 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:18 p.m.