Triple
T12573199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese fishing nets |
E295654
|
entity |
| Predicate | possibleIntroducedBy |
P91802
|
FINISHED |
| Object | Chinese traders |
—
|
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: Chinese traders | Statement: [Chinese fishing nets, possibleIntroducedBy, Chinese traders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleIntroducedBy Context triple: [Chinese fishing nets, possibleIntroducedBy, Chinese traders]
-
A.
oftenIntroducedBy
Indicates that one entity is frequently presented, mentioned, or brought into context by another entity.
-
B.
introduced
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
-
C.
introducedVia
Indicates that one entity was brought to the attention, presence, or awareness of another entity through a specific intermediary, method, or channel.
-
D.
areIntroducedBy
chosen
Indicates that one entity becomes known or presented to another entity through the action or mediation of a third party or process.
-
E.
coIntroduced
Indicates that two or more entities jointly introduced or presented something together for the first time.
- 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_69d6ad9cac2c81908e8a7bed82d1e21d |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d9550d84908190aea0f50055f6d92e |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95414692881909c52a1de7d224b44 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 11:50 p.m.