Triple
T19949516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indianization of Southeast Asia |
E479516
|
entity |
| Predicate | hasKeyMechanism |
P8166
|
FINISHED |
| Object | maritime trade |
—
|
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: maritime trade | Statement: [Indianization of Southeast Asia, hasKeyMechanism, maritime trade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyMechanism Context triple: [Indianization of Southeast Asia, hasKeyMechanism, maritime trade]
-
A.
hasMechanism
chosen
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
-
B.
hasKeyMaterial
Indicates that an entity possesses or contains the cryptographic key material required for encryption, decryption, or related security operations.
-
C.
hasKeyStrength
Indicates that an entity possesses a primary or defining strength, capability, or advantage.
-
D.
hasKeyPass
Indicates that an entity possesses or is granted a key-based pass that allows access or authorization to something.
-
E.
hasKeyAgreement
Indicates that two parties share or have established a cryptographic key agreement used to securely derive a common secret key.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a6a93548190875af2176e6901a7 |
completed | April 20, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.