Triple
T38464629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fake Crash |
E912531
|
entity |
| Predicate | hasLaterDeveloperContext |
P201799
|
FINISHED |
| Object | Vicarious Visions |
—
|
NE NERFINISHED |
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: Vicarious Visions | Statement: [Fake Crash, hasLaterDeveloperContext, Vicarious Visions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaterDeveloperContext Context triple: [Fake Crash, hasLaterDeveloperContext, Vicarious Visions]
-
A.
hasLaterRole
Indicates that an entity holds or assumes a role that occurs after another role in time or sequence.
-
B.
developedBefore
Indicates that one entity was developed or created earlier in time than another entity.
-
C.
hasDeveloperType
Indicates that an entity is associated with a specific category or type of developer.
-
D.
hasSubsequentVersion
Indicates that one entity is a later or updated version that follows another entity in a version sequence.
-
E.
hasDevelopmentType
Indicates the type or category of development associated with an entity, such as the nature, form, or stage of its development.
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a002249ee388190a9501ee7630dc658 |
completed | May 10, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_6a002189273881909b6b687e2d61f5b1 |
completed | May 10, 2026, 6:11 a.m. |
| PDg | Predicate description generation | batch_6a0022494be881908bdf945d2393a40f |
completed | May 10, 2026, 6:14 a.m. |
Created at: May 3, 2026, 4:31 p.m.