Triple
T15600929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ásbrú |
E375029
|
entity |
| Predicate | connectsWorld |
P119402
|
FINISHED |
| Object | world of gods |
—
|
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: world of gods | Statement: [Ásbrú, connectsWorld, world of gods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsWorld Context triple: [Ásbrú, connectsWorld, world of gods]
-
A.
connectsCountryOrRegion
Indicates that one entity establishes a connection, link, or association to a specific country or region.
-
B.
connectsCountryDirection
Indicates that one country is geographically connected to another in a specified cardinal or relative direction (e.g., north, south, east, west).
-
C.
connectsCommunities
Indicates a relationship in which something links or brings together separate communities, enabling interaction, communication, or shared activity between them.
-
D.
connectsCommunity
Indicates a relationship where an entity links or brings together members or groups within a community, fostering interaction or cohesion among them.
-
E.
connectsOcean
Indicates that one geographic entity serves as a link or passage between another entity and an ocean.
- 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_69d85cce25008190b13b52745fbd719b |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e621fc4819097e8e85e7ddfdc6c |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:12 a.m.