Triple
T25253532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Mississippi |
E632806
|
entity |
| Predicate | flagshipOf |
P4684
|
FINISHED |
| Object |
East India Squadron
The East India Squadron was a 19th-century United States Navy formation tasked with protecting American interests and conducting diplomacy and trade operations in East Asian waters.
|
E1671634
|
NE 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: East India Squadron | Statement: [USS Mississippi, flagshipOf, East India Squadron]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: East India Squadron Triple: [USS Mississippi, flagshipOf, East India Squadron]
Generated description
The East India Squadron was a 19th-century United States Navy formation tasked with protecting American interests and conducting diplomacy and trade operations in East Asian waters.
Provenance (5 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_69e75a8fdd3881909ba0b05aa5da92a7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4808e7b288190ad7444ccbef04d80 |
completed | May 1, 2026, 10:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1067efaf9c81908f825ad8d6426cd5 |
completed | May 22, 2026, 2:27 p.m. |
| NEDg | Description generation | batch_6a1068ad981081908f324aa1d7cc5bb2 |
completed | May 22, 2026, 2:31 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a106a12f4e08190a51c4cecf7a5de2a |
completed | May 22, 2026, 2:37 p.m. |
Created at: April 21, 2026, 1:11 p.m.