Triple
T15393854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lædingr |
E368117
|
entity |
| Predicate | attemptNumber |
P118608
|
FINISHED |
| Object | first chain used to bind Fenrir |
—
|
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: first chain used to bind Fenrir | Statement: [Lædingr, attemptNumber, first chain used to bind Fenrir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attemptNumber Context triple: [Lædingr, attemptNumber, first chain used to bind Fenrir]
-
A.
launchAttemptNumber
Indicates the ordinal count of attempts made to launch something, typically specifying which numbered try a particular launch event represents.
-
B.
attemptLimit
Indicates a restriction on how many times an action or operation may be attempted before it is stopped or blocked.
-
C.
rescueAttemptNumber
Indicates the ordinal count of distinct attempts made to carry out a rescue in a given rescue situation or operation.
-
D.
completionAttemptsBy
Indicates that a specific entity’s completion attempts are attributed to or performed by another entity.
-
E.
triedAt
Indicates that an attempt to perform an action or achieve an outcome occurred at a specific time or place.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e7838b48190862b43c6c8620692 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:19 a.m.