Triple
T33771398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingsman armory |
E865390
|
entity |
| Predicate | locatedUnderCoverOf |
P189936
|
FINISHED |
| Object | Kingsman tailor shop |
E244894
|
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: Kingsman tailor shop | Statement: [Kingsman armory, locatedUnderCoverOf, Kingsman tailor shop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedUnderCoverOf Context triple: [Kingsman armory, locatedUnderCoverOf, Kingsman tailor shop]
-
A.
undercoverIn
Indicates that an entity is secretly operating within a group, organization, or environment under false or concealed identity.
-
B.
coverUpBy
Indicates that one entity conceals, suppresses, or hides the actions, information, or wrongdoing associated with another entity.
-
C.
isCoveredIn
Indicates that one entity has its surface or area overlaid, coated, or blanketed by another substance or material.
-
D.
hiddenByMeansOf
chosen
Indicates that one entity is concealed or obscured through the use or application of another entity as the means of hiding.
-
E.
laterCoveredBy
Indicates that one event, state, or interval is temporally followed and then overlapped or encompassed by another that occurs later.
- F. None of above.
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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36657f2fd88190b998716a713f4730 |
completed | June 20, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:45 a.m.