Triple
T1919780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SKOS |
E40098
|
entity |
| Predicate | hasMappingProperty |
P33157
|
FINISHED |
| Object | skos:exactMatch |
—
|
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: skos:exactMatch | Statement: [SKOS, hasMappingProperty, skos:exactMatch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMappingProperty Context triple: [SKOS, hasMappingProperty, skos:exactMatch]
-
A.
haveProperty
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
-
B.
hasMapReference
Indicates that an entity is associated with a specific map or map location reference.
-
C.
hasPropertyType
Indicates that an entity possesses or is associated with a specific type or category of property.
-
D.
hasIndex
Indicates that one entity serves as an index or positional reference for another entity within an ordered collection or structure.
-
E.
hasKeyRelationship
Indicates a relationship where one entity serves as a key (e.g., identifier, access token, or primary reference) that grants access to, controls, or uniquely identifies another entity.
- 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb213af0481909429ec971860a3fd |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafed2ab481908920334e77b1021b |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb1b180e481908bbe893d6ba6208b |
completed | March 7, 2026, 5:03 a.m. |
Created at: March 4, 2026, 7:35 p.m.