Triple
T11394610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indonesian Throughflow |
E269939
|
entity |
| Predicate | typicalNetTransport |
P99080
|
FINISHED |
| Object | about 15 Sverdrups |
—
|
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: about 15 Sverdrups | Statement: [Indonesian Throughflow, typicalNetTransport, about 15 Sverdrups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalNetTransport Context triple: [Indonesian Throughflow, typicalNetTransport, about 15 Sverdrups]
-
A.
transportProtocol
Indicates the communication protocol used to transport data between entities in a networked interaction.
-
B.
typicalTransportObject
Indicates that one entity is a typical or commonly used object for transporting or carrying the other entity.
-
C.
typicalPort
Indicates that a specified port is commonly or normally used for a given service, protocol, or application.
-
D.
baseTransmission
Indicates the fundamental or default mode by which something is transmitted or passed from one entity to another.
-
E.
typicalInfrastructure
Indicates that something is part of the standard or commonly expected infrastructure associated with a given context or entity.
- F. None of above. chosen
Provenance (4 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d80018a58c81908b80dc9abd18d650 |
completed | April 9, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69d7e70b228c8190b87f5101fd683788 |
completed | April 9, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69d80010712c819089ea2e31e664abe1 |
completed | April 9, 2026, 7:37 p.m. |
Created at: April 8, 2026, 9:34 p.m.