Triple
T31023250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ictíneo I |
E790503
|
entity |
| Predicate | locatedInPresent |
P145498
|
FINISHED |
| Object | no surviving original hull |
—
|
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: no surviving original hull | Statement: [Ictíneo I, locatedInPresent, no surviving original hull]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInPresent Context triple: [Ictíneo I, locatedInPresent, no surviving original hull]
-
A.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
B.
currentlyLocatedAt
chosen
Indicates that an entity’s present or most recent known physical location is at the specified place.
-
C.
locationPresented
Indicates that a specific location is presented or shown to an entity (such as a user or system) within a given context.
-
D.
locatedWith
Indicates that two or more entities are situated together in the same place or spatial context.
-
E.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a013e23698c81909a32d371b6f158d0 |
completed | May 11, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_6a013db04b108190985897aa6e95b4ec |
completed | May 11, 2026, 2:23 a.m. |
Created at: April 29, 2026, 8:58 p.m.