Triple
T9562931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T2 tanker |
E230718
|
entity |
| Predicate | typicalDraft |
P89807
|
FINISHED |
| Object | approximately 30 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: approximately 30 feet | Statement: [T2 tanker, typicalDraft, approximately 30 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDraft Context triple: [T2 tanker, typicalDraft, approximately 30 feet]
-
A.
draftedIn
Indicates that one entity was selected or recruited into another entity (such as a team, organization, or military service) through a formal draft process.
-
B.
ドラフト種別
Indicates the type or category of a draft in relation to how it was created, selected, or classified.
-
C.
draftedAt
Indicates that an entity was selected or chosen by another entity at a specific draft event or position.
-
D.
notableDraftPick
Indicates that an entity was a particularly significant or distinguished selection in a draft event (such as a sports or professional draft).
-
E.
draftedUnder
Indicates that one entity was formally selected or conscripted into a role, position, or service according to the authority, rules, or jurisdiction of another entity.
- 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_69ca847e53a88190a60eed7e02257f10 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9965e7b881909df98e933db38092 |
completed | April 1, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69ccd594d0ac8190a81bc11a3a538167 |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93e90048190a2b0d7c5c195ba98 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:03 p.m.