Triple
T35360451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ray |
E1021460
|
entity |
| Predicate | hasAliasContext |
P46158
|
FINISHED |
| Object | Ray from In Bruges |
—
|
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: Ray from In Bruges | Statement: [Ray, hasAliasContext, Ray from In Bruges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAliasContext Context triple: [Ray, hasAliasContext, Ray from In Bruges]
-
A.
hasAliasReference
Indicates that one entity serves as an alternate name or alias referring to another entity.
-
B.
hasAlternativeContext
chosen
Indicates that something is associated with an additional or different contextual setting or interpretation beyond its primary one.
-
C.
hasAliasUser
Indicates that a user is known or referred to by an alternative name or identifier.
-
D.
hasLocalContext
Indicates that something exists or occurs within a specific, surrounding situational or environmental context tied to a particular place or scope.
-
E.
usesAliasIn
Indicates that one entity operates under or refers to another entity by an alternative name or alias within a specific context.
- 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_69f76def44c881908a20e8008572eb44 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: May 3, 2026, 4:03 p.m.