Triple
T33942656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Godspeed (ship) |
E870205
|
entity |
| Predicate | replicaBuiltFor |
P177948
|
FINISHED |
| Object | educational and commemorative purposes |
—
|
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: educational and commemorative purposes | Statement: [Godspeed (ship), replicaBuiltFor, educational and commemorative purposes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replicaBuiltFor Context triple: [Godspeed (ship), replicaBuiltFor, educational and commemorative purposes]
-
A.
replicaBuilt
Indicates that one entity has been constructed as a copy or reproduction of another entity.
-
B.
replicaOf
Indicates that one entity is an exact or near-exact copy of another entity, preserving its form, structure, or content.
-
C.
hasReplicaBuilding
Indicates that one building serves as a replica or reproduction of another building.
-
D.
replicaLocation
Indicates the physical or logical place where a copy or replica of an item, resource, or data set is stored or maintained.
-
E.
reconstructionBuiltAt
Indicates that a reconstruction of something was built or carried out at a specific location or site.
- 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f7064d37388190993b2a7305a02b9f |
completed | May 3, 2026, 8:24 a.m. |
Created at: May 1, 2026, 1:49 a.m.