Triple
T27978321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Szare Szeregi |
E706548
|
entity |
| Predicate | usedCodenameFor |
P61115
|
FINISHED |
| Object | underground Polish Scouting resistance |
—
|
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: underground Polish Scouting resistance | Statement: [Szare Szeregi, usedCodenameFor, underground Polish Scouting resistance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedCodenameFor Context triple: [Szare Szeregi, usedCodenameFor, underground Polish Scouting resistance]
-
A.
endUseAsCodename
Indicates that an entity stops being used as a codename for another entity or concept.
-
B.
usesCodeName
chosen
Indicates that one entity refers to another entity by a code name or alias instead of its real or full designation.
-
C.
relatedCodename
Indicates that one entity has an associated or connected codename that is contextually related to it.
-
D.
translationOfCodename
Indicates that one codename is a translated version of another codename, preserving its intended meaning across languages.
-
E.
codenameUser
Indicates that a user is assigned or associated with a particular codename.
- 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 7:42 p.m.