Triple
T547553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Ocean trade network |
E12764
|
entity |
| Predicate | involvedActor |
P15562
|
FINISHED |
| Object | Arab merchants |
—
|
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: Arab merchants | Statement: [Indian Ocean trade network, involvedActor, Arab merchants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedActor Context triple: [Indian Ocean trade network, involvedActor, Arab merchants]
-
A.
playedBy
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
B.
starredActor
Indicates that an actor performed a leading or significant role in a particular production or work.
-
C.
oftenPlayedBy
Indicates that one entity frequently performs, portrays, or executes another entity, such as a role, character, or piece of music.
-
D.
notableCastMember
Indicates that an entity is a member of the cast of another entity (such as a film, show, or production) and is considered particularly notable or significant in that role.
-
E.
portrayedBy
Indicates that one entity serves as the actor or performer who represents or plays the role of another entity in a work or medium.
- 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_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. |
| PDg | Predicate description generation | batch_69a49858abd48190bd4b002a93e4a908 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.