Triple
T11556500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Citium |
E274030
|
entity |
| Predicate | connectedByTradeTo |
P12536
|
FINISHED |
| Object | Phoenician cities |
—
|
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: Phoenician cities | Statement: [Citium, connectedByTradeTo, Phoenician cities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedByTradeTo Context triple: [Citium, connectedByTradeTo, Phoenician cities]
-
A.
tradedTo
Indicates that ownership or contractual rights to an entity (such as a player, asset, or item) were transferred from one party to another, typically as part of an exchange or deal.
-
B.
formerlyConnectedTo
Indicates that two entities were once connected or associated in some way, but that connection no longer exists.
-
C.
sharesTradedFor
Indicates that shares of one entity are exchanged or traded in return for another asset, security, or form of consideration.
-
D.
tradesAs
Indicates that one entity conducts business or is publicly known under the trading name or brand of another entity.
-
E.
hasTrade
chosen
Indicates a relationship where one entity engages in or maintains a commercial exchange or trading activity with 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88a86be308190973fea5d7db8ba9d |
completed | April 10, 2026, 5:28 a.m. |
| PD | Predicate disambiguation | batch_69d85dc3fc2c8190bed7e2111301a77c |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:37 p.m.