Triple
T7411471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loch Ness Monster |
E171012
|
entity |
| Predicate | reportedBehavior |
P23475
|
FINISHED |
| Object | surfacing occasionally |
—
|
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: surfacing occasionally | Statement: [Loch Ness Monster, reportedBehavior, surfacing occasionally]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportedBehavior Context triple: [Loch Ness Monster, reportedBehavior, surfacing occasionally]
-
A.
behaviorObserved
chosen
Indicates that a particular behavior or action has been witnessed, recorded, or detected in relation to an entity or context.
-
B.
reportedMarks
Indicates that an entity has formally communicated or submitted the marks/grades of another entity (such as a student or assessment) to a relevant party or system.
-
C.
scoreReportedTo
Indicates that a score or result has been communicated or submitted from one party to another.
-
D.
reportedOn
Indicates that one entity has provided an account, description, or coverage of another entity, typically as news, documentation, or an official report.
-
E.
mayReportTo
Indicates that one entity is permitted or allowed to have a reporting relationship to another entity, such as an employee being allowed to report to a particular manager.
- 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_69c6f2a027148190bdb6a7940389e377 |
completed | March 27, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:11 p.m.