Triple
T37874498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elder Rifts |
E944682
|
entity |
| Predicate | hasRunTime |
P74363
|
FINISHED |
| Object | short session content |
—
|
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: short session content | Statement: [Elder Rifts, hasRunTime, short session content]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRunTime Context triple: [Elder Rifts, hasRunTime, short session content]
-
A.
hasRun
Indicates that an entity has performed or completed a running activity or event at least once in the past.
-
B.
hasRunType
Indicates the type or category of a run associated with an entity (e.g., execution mode, run classification, or run configuration).
-
C.
hasRunningTimeCategory
chosen
Indicates that an entity is associated with a specific category based on its running time or duration.
-
D.
hasRuntimeType
Indicates that an entity is of, or conforms to, a specific type when evaluated at runtime rather than at compile time.
-
E.
hasWorkRuntimeAppearedIn
Indicates that a particular work runtime has been featured or included in a specified context, such as a release, edition, or presentation.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:19 p.m.