Triple
T8716252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panamax |
E206900
|
entity |
| Predicate | hasMaxDraft |
P34007
|
FINISHED |
| Object | about 39.5 feet |
—
|
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: about 39.5 feet | Statement: [Panamax, hasMaxDraft, about 39.5 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaxDraft Context triple: [Panamax, hasMaxDraft, about 39.5 feet]
-
A.
hasMaxDraftApprox
chosen
Indicates that one entity has, as an upper bound, an approximate maximum value or level for a draft-related quantity associated with another entity.
-
B.
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.
-
C.
hasDraft
Indicates that one entity possesses or is associated with a preliminary or unfinished version of another entity.
-
D.
hasDraftedPlayersTo
Indicates that one entity has selected or drafted players to join or belong to another entity, such as a team, league, or organization.
-
E.
hasDraftOrAssignmentSystem
Indicates that an entity possesses or is associated with a system for managing drafts or assignments.
- 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5cd9c2a08190a65ab0ce573153d2 |
completed | March 31, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.