Triple
T35010183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raven Rock |
E1009920
|
entity |
| Predicate | hasTerminalEntries |
P107095
|
FINISHED |
| Object | Enclave logs |
—
|
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: Enclave logs | Statement: [Raven Rock, hasTerminalEntries, Enclave logs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerminalEntries Context triple: [Raven Rock, hasTerminalEntries, Enclave logs]
-
A.
hasTerminals
chosen
Indicates that one entity possesses, contains, or is associated with one or more terminal points, endpoints, or terminal elements of another entity.
-
B.
hasSubTerminal
Indicates that an entity includes or is associated with a subordinate or lower-level terminal element within a hierarchical structure.
-
C.
hasTerminusIn
Indicates that something (such as a route, line, or path) ends or has its final stopping point at a specified location.
-
D.
hasTerminalFunction
Indicates that something possesses a function or role specifically associated with an endpoint, boundary, or final stage within a system or process.
-
E.
hasTerminalShape
Indicates that one entity possesses or exhibits a particular terminal (end) shape defined by another entity.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
Created at: May 3, 2026, 4:01 p.m.