Triple
T33093817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Master Gunnery Sergeant (USMC) |
E846853
|
entity |
| Predicate | typicalAddress |
P89231
|
FINISHED |
| Object | Master Guns |
—
|
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: Master Guns | Statement: [Master Gunnery Sergeant (USMC), typicalAddress, Master Guns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAddress Context triple: [Master Gunnery Sergeant (USMC), typicalAddress, Master Guns]
-
A.
typicalDestinationAddress
Indicates the address that is most commonly or usually used as the destination for something or someone.
-
B.
traditionalAddress
chosen
Indicates that one entity is the conventional or customary form of address (e.g., title, honorific, or name) used for referring to another entity.
-
C.
addressType
Indicates the specific kind or category of address associated with an entity (e.g., home, work, billing, or shipping).
-
D.
typeOfAddress
Indicates the specific category or kind of address (e.g., home, work, billing) associated with an entity.
-
E.
streetAddress
Indicates the specific location of an entity in terms of its numbered building and street name within a postal address.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:26 a.m.