Triple
T25288936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamrun |
E634025
|
entity |
| Predicate | knownByEuropeanTradersAs |
P14444
|
FINISHED |
| Object | Gombroon |
—
|
NE NERFINISHED |
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: Gombroon | Statement: [Gamrun, knownByEuropeanTradersAs, Gombroon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownByEuropeanTradersAs Context triple: [Gamrun, knownByEuropeanTradersAs, Gombroon]
-
A.
oftenRecognizedBy
Indicates that one entity is frequently identified, acknowledged, or noticed by another entity.
-
B.
regionallyKnownAs
chosen
Indicates that an entity is known by a particular name or designation within a specific geographic region.
-
C.
historicallyRecognizedAs
Indicates that an entity has been acknowledged or designated under a particular name, status, or role during a past historical period.
-
D.
traditionallyKnownFor
Indicates that something is widely and historically recognized or reputed for a particular characteristic, activity, product, or role.
-
E.
eraOfDiscovery
Indicates a relationship where something belongs to, occurs in, or is characteristic of a specific era of discovery or exploration.
- 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 1:21 p.m.