Triple
T26273125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacArthur Lock |
E660485
|
entity |
| Predicate | isMajorLockInComplex |
P171746
|
FINISHED |
| Object | Soo Locks |
—
|
NE NERFINISHED |
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: Soo Locks | Statement: [MacArthur Lock, isMajorLockInComplex, Soo Locks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorLockInComplex Context triple: [MacArthur Lock, isMajorLockInComplex, Soo Locks]
-
A.
isMajorLockOf
chosen
Indicates that one lock functions as the primary or controlling lock for another lock or set of locks.
-
B.
isMajorComplexIn
Indicates that one entity is the primary or major complex located within, or functionally contained in, another entity.
-
C.
isMajorFor
Indicates that one entity serves as the primary field of academic specialization (major) for another entity, typically a student.
-
D.
isMajorSeeWithin
Indicates that one entity is the primary or most significant location or area encompassed within the boundaries of another entity.
-
E.
isMajor
Indicates that an entity holds primary or greater significance, importance, or rank relative to others in a given context.
- 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 26, 2026, 9:52 p.m.