Triple
T32027388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navy Supply Corps School |
E817854
|
entity |
| Predicate | movedToNewport |
P173135
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Navy Supply Corps School, movedToNewport, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movedToNewport Context triple: [Navy Supply Corps School, movedToNewport, 2011]
-
A.
movedOn
Indicates that an entity changed its position or location from one place to another at some point in time.
-
B.
movedToAugusta
Indicates that an entity changed its place of residence or location to Augusta.
-
C.
movedFor
Indicates that one entity changed its location or position for the benefit, purpose, or in response to another entity.
-
D.
movedIn
Indicates that an entity has taken up residence or established occupancy at a new location or dwelling.
-
E.
movedToHokkaido
Indicates that an entity changed their place of residence or primary location to Hokkaido.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b46ac390819092125a5e03b66b63 |
completed | May 3, 2026, 2:35 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b21da77081908c5c015c4606d344 |
completed | May 3, 2026, 2:25 a.m. |
Created at: May 1, 2026, 12:17 a.m.