Triple
T1840427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neopanamax |
E41164
|
entity |
| Predicate | hasMaxDraftApprox |
P34007
|
FINISHED |
| Object | 15.2 metres |
—
|
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: 15.2 metres | Statement: [Neopanamax, hasMaxDraftApprox, 15.2 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaxDraftApprox Context triple: [Neopanamax, hasMaxDraftApprox, 15.2 metres]
-
A.
maximumDraft
Indicates that there is an upper limit on the number of drafts that can be created, stored, or associated with a given entity or process.
-
B.
hasDraft
Indicates that one entity possesses or is associated with a preliminary or unfinished version of another entity.
-
C.
hasDraftedPlayersTo
Indicates that one entity has selected or drafted players to join or belong to another entity, such as a team, league, or organization.
-
D.
hasApproximateMaximumWidth
Indicates that an entity’s maximum width is known only approximately, rather than as an exact value.
-
E.
hasMaximumValue
Indicates that one value in a set is the greatest or highest possible according to a specified criterion.
- 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_69a88647f9388190909bc36e795bdaec |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdb0d2c8190a67f584e67979fa3 |
completed | March 7, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69abb32a8d548190a231c7c2ce276a5e |
completed | March 7, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:33 p.m.