Triple
T24431171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashley Williams |
E616004
|
entity |
| Predicate | romanceAvailableTo |
P156105
|
FINISHED |
| Object | male Shepard |
—
|
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: male Shepard | Statement: [Ashley Williams, romanceAvailableTo, male Shepard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanceAvailableTo Context triple: [Ashley Williams, romanceAvailableTo, male Shepard]
-
A.
encouragesRomanceBetween
Indicates that one entity promotes, supports, or fosters a romantic relationship between two other entities.
-
B.
canRomanceMultipleCharacters
Indicates that an entity is able to pursue romantic relationships with more than one character.
-
C.
romanceObstructedBy
Indicates that a romantic relationship or potential romance is being hindered, blocked, or prevented by some opposing factor or circumstance.
-
D.
hasRomanticPlotline
Indicates that there is a romantic storyline or relationship development present between the entities.
-
E.
hasRomanticMisadventures
Indicates that an entity experiences a series of problematic, comical, or unsuccessful romantic relationships or encounters.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29782a4a0819087cb7ba399371520 |
completed | April 29, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:16 a.m.