Triple
T28969695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonet |
E734236
|
entity |
| Predicate | proposedPortStatus |
P59932
|
FINISHED |
| Object | not built as of early 2020s |
—
|
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: not built as of early 2020s | Statement: [Colonet, proposedPortStatus, not built as of early 2020s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedPortStatus Context triple: [Colonet, proposedPortStatus, not built as of early 2020s]
-
A.
proposedPortIntendedFor
Indicates that a suggested or planned port is meant to be used for a particular purpose, service, or connection.
-
B.
hasPortStatus
chosen
Indicates the current operational or connectivity state of a specific port in a system or device.
-
C.
proposedPortDeveloperCandidate
Indicates that an entity has been put forward as a candidate to serve as the developer for a specific port project.
-
D.
freePortStatusGrantedBy
Indicates that a free port status has been conferred upon an entity by a specific granting authority or decision.
-
E.
proposerState
Indicates the current status or condition of a proposer within a proposal or decision-making process.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 28, 2026, 9:04 a.m.