Triple
T15428080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Móðguðr |
E369564
|
entity |
| Predicate | asksQuestionsOf |
P111446
|
FINISHED |
| Object | travelers crossing Gjallarbrú |
—
|
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: travelers crossing Gjallarbrú | Statement: [Móðguðr, asksQuestionsOf, travelers crossing Gjallarbrú]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: asksQuestionsOf Context triple: [Móðguðr, asksQuestionsOf, travelers crossing Gjallarbrú]
-
A.
questionAsksWhether
Indicates that one entity poses a question to determine if a particular condition, fact, or proposition is true or not.
-
B.
questionPresented
chosen
Indicates that a question has been posed or displayed to an entity for consideration or response.
-
C.
canAnswerQuestions
Indicates that an entity has the ability or capacity to respond correctly or appropriately to questions.
-
D.
questionConveyedBy
Indicates that a particular question is expressed, communicated, or represented by a given medium, message, or artifact.
-
E.
raisesQuestion
Indicates that one entity causes or prompts a question or doubt to arise about another entity or topic.
- 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ec31f4881908b26ff7c381d7bc9 |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:20 a.m.