Triple
T36851097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quest for Glory series |
E910677
|
entity |
| Predicate | typicalClasses |
P62073
|
FINISHED |
| Object | fighter |
—
|
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: fighter | Statement: [Quest for Glory series, typicalClasses, fighter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalClasses Context triple: [Quest for Glory series, typicalClasses, fighter]
-
A.
typicalCaseTypes
Indicates the kinds or categories of cases that are most commonly associated with or handled by a given entity.
-
B.
typicalFunctionClass
Indicates that something belongs to the usual or characteristic functional category associated with it.
-
C.
mainClasses
Indicates that the subject represents the primary or most important classes associated with, defined within, or central to the object.
-
D.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
-
E.
typicalGroup
chosen
Indicates that the subject belongs to or represents a standard, characteristic, or commonly occurring group associated with the object.
- 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.