Triple
T17780428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Land art |
E443877
|
entity |
| Predicate | documentationShownIn |
P128902
|
FINISHED |
| Object | museums |
—
|
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: museums | Statement: [Land art, documentationShownIn, museums]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentationShownIn Context triple: [Land art, documentationShownIn, museums]
-
A.
documentationUI
Indicates a relationship where a user interface element is used to present, navigate, or interact with documentation content.
-
B.
documentationSection
Indicates that one entity is a specific section or subdivision within the documentation of another entity.
-
C.
documentedUsing
Indicates that something is recorded, described, or specified by means of a particular document, tool, or documentation method.
-
D.
documentedThrough
Indicates that something is recorded, evidenced, or made known by means of a specific document or documentation process.
-
E.
documentationContext
Indicates the situational or surrounding information in which documentation is created, used, or interpreted.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4872152508190870a1765e0972ec1 |
completed | April 19, 2026, 7:41 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:12 a.m.