Triple
T2040366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mosaic |
E44728
|
entity |
| Predicate | supportsHyperlinks |
P30776
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mosaic, supportsHyperlinks, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsHyperlinks Context triple: [Mosaic, supportsHyperlinks, true]
-
A.
supportsLinks
chosen
Indicates that one entity provides backing, endorsement, or assistance to another entity through connections or references (such as hyperlinks or relational links).
-
B.
supportsOffice
Indicates that one entity provides assistance, resources, or endorsement to an office or officeholder in performing its functions or maintaining its operations.
-
C.
supportsLinkedData
Indicates that one entity provides or enables functionality for using, publishing, or interacting with Linked Data associated with another entity.
-
D.
supportsDocument
Indicates that one entity provides compatibility or functionality for handling, processing, or using a particular document or document type.
-
E.
linkedDocument
Indicates that one document is associated with or references another document in a meaningful way.
- 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_69a889159ec481908f9e4472d9f480c7 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abbc2c3f6c8190aff07097b2654e52 |
completed | March 7, 2026, 5:48 a.m. |
| PD | Predicate disambiguation | batch_69abb7aa00d4819086d347d9a08f81a0 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.