Triple
T2926291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brocken spectre |
E78851
|
entity |
| Predicate | isDocumentedSince |
P28519
|
FINISHED |
| Object | at least the 18th century |
—
|
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: at least the 18th century | Statement: [Brocken spectre, isDocumentedSince, at least the 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDocumentedSince Context triple: [Brocken spectre, isDocumentedSince, at least the 18th century]
-
A.
hasFirstDocumentedUse
chosen
Indicates that one entity is the earliest known or recorded instance in which the other entity was used or attested.
-
B.
documentedUsing
Indicates that something is recorded, described, or specified by means of a particular document, tool, or documentation method.
-
C.
hasDocumentationAt
Indicates that something is documented or described in a specific document, file, or location.
-
D.
introducedWithVersion
Indicates that something first became available or was added starting from a specific version.
-
E.
hasLimitedDocumentation
Indicates that the subject is associated with documentation that is sparse, incomplete, or not sufficiently detailed.
- 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_69ad8b0d40b481908bc2a5fa2e73c3fb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97fd89d88190bc7db4b39058ae3a |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9606e8348190bb19df33a2709674 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:55 p.m.