Triple
T547513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Ocean trade network |
E12764
|
entity |
| Predicate | facilitated |
P1710
|
FINISHED |
| Object | long-distance 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: long-distance maritime trade | Statement: [Indian Ocean trade network, facilitated, long-distance maritime trade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facilitated Context triple: [Indian Ocean trade network, facilitated, long-distance maritime trade]
-
A.
coFacilitatedBy
Indicates that an activity, process, or event is jointly led, guided, or managed by the referenced entity.
-
B.
favored
Indicates that one entity is preferred, supported, or given advantage over others by another entity.
-
C.
accessible
chosen
Indicates that one entity can be reached, entered, used, or understood by another entity, often without undue difficulty or barriers.
-
D.
controlled
Indicates that one entity has power, authority, or influence to direct, regulate, or determine the behavior, actions, or state of another entity.
-
E.
relievedBy
Indicates that one entity eases, reduces, or removes the burden, pain, stress, or responsibility experienced by another entity.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a498e2e8c88190a66d759ed3094e18 |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494b957988190bc269e372df2f0b2 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.