Triple
T35889797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domini di Terraferma |
E1037749
|
entity |
| Predicate | expansionMotivation |
P38715
|
FINISHED |
| Object | control of trade routes |
—
|
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: control of trade routes | Statement: [Domini di Terraferma, expansionMotivation, control of trade routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionMotivation Context triple: [Domini di Terraferma, expansionMotivation, control of trade routes]
-
A.
expansionReason
chosen
Indicates the reason or cause behind an expansion event or process occurring between entities.
-
B.
expands
Indicates that one entity increases in size, volume, scope, or extent relative to a previous state or another entity.
-
C.
limitsExpansionOf
Indicates that one entity restricts or constrains the growth, spread, or further development of another entity.
-
D.
expansionAdded
Indicates that an additional component, feature, or content has been incorporated into an existing entity or system.
-
E.
supportedExpansionOf
Indicates that one entity actively aided, endorsed, or facilitated the growth, extension, or enlargement of another entity or domain.
- 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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:06 p.m.