Triple
T2383999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward Leader Williams |
E46374
|
entity |
| Predicate | hasNotableProjectType |
P12865
|
FINISHED |
| Object | ship canal |
—
|
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: ship canal | Statement: [Edward Leader Williams, hasNotableProjectType, ship canal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableProjectType Context triple: [Edward Leader Williams, hasNotableProjectType, ship canal]
-
A.
hasProjectType
chosen
Indicates that an entity is associated with, or classified under, a specific type or category of project.
-
B.
hasProject
Indicates that an entity is associated with or responsible for a particular project.
-
C.
hasNotableProject
Indicates that an entity is associated with a project that is distinguished or recognized as significant in some way.
-
D.
supportsProjectType
Indicates that one entity is capable of handling, accommodating, or being compatible with a specified type of project.
-
E.
hasNotableType
Indicates that an entity is associated with a specific notable category or type that characterizes its significance or role.
- 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_69a88a1554a48190a0180682bcf099be |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc7bc87d0819090cd9d19d748bcc3 |
completed | March 7, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69abc59f73f08190924a36d7d475d8f4 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.