Triple
T3736676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neckar |
E79602
|
entity |
| Predicate | hasLocks |
P2430
|
FINISHED |
| Object | multiple navigation locks |
—
|
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: multiple navigation locks | Statement: [Neckar, hasLocks, multiple navigation locks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocks Context triple: [Neckar, hasLocks, multiple navigation locks]
-
A.
hasLock
Indicates that one entity possesses or is secured by a lock associated with another entity.
-
B.
hasNumberOfLocks
chosen
Indicates the quantity of locks that an entity possesses or is equipped with.
-
C.
hasLockType
Indicates that an entity is associated with or uses a specific type or category of lock.
-
D.
areLockedIn
Indicates that the entities are confined within a space or situation from which they cannot freely exit or escape.
-
E.
hasMultipleHoldersSimultaneously
Indicates that a given item, role, or resource is concurrently possessed, controlled, or occupied by more than one holder at the same time.
- 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb3d32b081909a993a78b0869db8 |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc04746588190b0dc535638f23546 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.