Triple
T38189738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guichen Bay |
E1005419
|
entity |
| Predicate | hasNearbyPortHistory |
P125751
|
FINISHED |
| Object | Robe as historic port |
—
|
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: Robe as historic port | Statement: [Guichen Bay, hasNearbyPortHistory, Robe as historic port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyPortHistory Context triple: [Guichen Bay, hasNearbyPortHistory, Robe as historic port]
-
A.
hasPortHistory
Indicates that an entity has an associated record or log of its past port-related events, visits, or configurations.
-
B.
hasHistoricPort
chosen
Indicates that an entity possesses or is associated with a port that has historical significance or longstanding historical use.
-
C.
hasNearbyPortAccess
Indicates that an entity is located close enough to a port to feasibly use it for access or transport.
-
D.
hasNearbyPortCountry
Indicates that one entity is a country that has a seaport located geographically close to the other entity.
-
E.
hasNearbyHistoricPeriod
Indicates that one historic period occurs close in time or space to another historic period.
- 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_69f76dbd22f48190940318cea061e8bb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00c07b302081908bf9755f8fdbc36e |
completed | May 10, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_6a00bfffb168819084b65804d601896d |
completed | May 10, 2026, 5:27 p.m. |
Created at: May 3, 2026, 4:29 p.m.