Triple
T7411443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loch Ness Monster |
E171012
|
entity |
| Predicate | firstModernReportYear |
P14790
|
FINISHED |
| Object | 1933 |
—
|
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: 1933 | Statement: [Loch Ness Monster, firstModernReportYear, 1933]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstModernReportYear Context triple: [Loch Ness Monster, firstModernReportYear, 1933]
-
A.
firstReportedYear
chosen
Indicates the year in which something was initially reported, documented, or made known for the first time.
-
B.
firstCreationYear
Indicates the year in which something was first created or originally produced.
-
C.
firstRunningYear
Indicates the year in which something (such as an event, service, or operation) first began running or was initially active.
-
D.
firstPermanentBaseYear
Indicates the year in which an entity’s first permanent base or facility was initially established.
-
E.
firstCompleterYear
Indicates the calendar or academic year in which an entity first completed a specified program, requirement, or activity.
- 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_69c68a618bdc81908d8018edadecd1a4 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f29ebea48190be96c6bc1e6406fb |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:11 p.m.