Triple
T30906005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moguer |
E787301
|
entity |
| Predicate | hasPortTradition |
P196215
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Moguer, hasPortTradition, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPortTradition Context triple: [Moguer, hasPortTradition, yes]
-
A.
hasTraditionIn
Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
-
B.
hasEndTradition
Indicates that an entity marks or represents the concluding part or final phase of a tradition.
-
C.
hasStageTradition
Indicates that an entity is associated with, follows, or embodies a particular stage or theatrical performance tradition.
-
D.
hasListTradition
Indicates that an entity maintains or follows a recognized tradition or customary practice of using lists.
-
E.
hasServiceTradition
Indicates that an entity maintains an established, customary way of providing a particular service over time.
- F. None of above. chosen
Provenance (4 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
| PDg | Predicate description generation | batch_69fe1639613c8190aaf1b4c8e2d861ba |
completed | May 8, 2026, 4:58 p.m. |
Created at: April 29, 2026, 8:50 p.m.