Triple
T35012788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jel |
E1009974
|
entity |
| Predicate | loreSourceType |
P182006
|
FINISHED |
| Object | in-game dialogue |
—
|
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: in-game dialogue | Statement: [Jel, loreSourceType, in-game dialogue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loreSourceType Context triple: [Jel, loreSourceType, in-game dialogue]
-
A.
loreType
Indicates the category or kind of lore that characterizes or classifies a given entity or subject.
-
B.
collectionOrigin
Indicates that one entity is the source, provenance, or originating context from which a collection of items or data has been derived or assembled.
-
C.
intelligenceSource
Indicates that one entity serves as the origin or provider of intelligence information for another entity.
-
D.
commonSources
Indicates that two or more entities share the same origin, cause, or source.
-
E.
knownFrom
Indicates that one entity is aware of, has learned about, or recognizes another entity through a specified source, context, or medium.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7865578d48190bf90e470634fd97d |
completed | May 3, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f78575917481909a3defd6a4c366bd |
completed | May 3, 2026, 5:27 p.m. |
Created at: May 3, 2026, 4:01 p.m.