Triple
T37552324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broken Isles Pathfinder, Part Two |
E933615
|
entity |
| Predicate | requirementType |
P202310
|
FINISHED |
| Object | exploration |
—
|
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: exploration | Statement: [Broken Isles Pathfinder, Part Two, requirementType, exploration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requirementType Context triple: [Broken Isles Pathfinder, Part Two, requirementType, exploration]
-
A.
typeOfRequirement
Indicates that one requirement is classified as a specific kind or category of another, more general requirement.
-
B.
typicalRequirement
Indicates that one entity is a standard or commonly expected prerequisite, condition, or necessity for another entity.
-
C.
qualificationRequirementType
Indicates the kind or category of qualification that is required in a given context or for a specific role, task, or opportunity.
-
D.
earnRequirementType
Indicates the type or category of requirement that must be fulfilled in order to earn or obtain something.
-
E.
componentRequirement
Indicates that one component depends on or necessitates the presence or use of another component to function or be considered complete.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00708ab11081909641d245c4282aa0 |
completed | May 10, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_6a00703daa0081908903ce3a28084d35 |
completed | May 10, 2026, 11:47 a.m. |
| PDg | Predicate description generation | batch_6a00708a01d08190a290fabcb435c358 |
completed | May 10, 2026, 11:48 a.m. |
Created at: May 3, 2026, 4:17 p.m.