Triple
T31575631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GLEX |
E805689
|
entity |
| Predicate | associatedWithRangeClass |
P207462
|
FINISHED |
| Object | long-range |
—
|
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: long-range | Statement: [GLEX, associatedWithRangeClass, long-range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithRangeClass Context triple: [GLEX, associatedWithRangeClass, long-range]
-
A.
associatedWithClass
Indicates that an entity has a connection or linkage to a particular class or category, without specifying the exact nature of that relationship.
-
B.
associatedRange
Indicates that one entity is linked to or falls within a particular range defined or referenced by another entity.
-
C.
associatedWithAssociation
Indicates a relationship where an entity is linked or connected to a particular association or organization.
-
D.
associatedWithCollection
Indicates that an entity has a relationship or linkage to a particular collection, such as being included in, managed by, or contextually grouped with that collection.
-
E.
associatedWithAttribute
Indicates that one entity is linked to, characterized by, or described through a particular attribute.
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 30, 2026, 10:21 p.m.