Triple
T7225855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian resistance movement |
E154776
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | XU |
E269013
|
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: XU | Statement: [Norwegian resistance movement, hasPart, XU]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: XU Context triple: [Norwegian resistance movement, hasPart, XU]
-
A.
XU
chosen
XU was a clandestine Norwegian intelligence organization that gathered and transmitted vital information to the Allies during the German occupation in World War II.
-
B.
YXU
YXU is the IATA airport code for London International Airport serving London, Ontario, Canada.
-
C.
Xing
Xing is a German-based professional networking platform focused on career development and business connections, particularly in German-speaking countries.
-
D.
XUA
XUA (Cross-Enterprise User Assertion) is an IHE IT Infrastructure profile that standardizes how user identity and authentication information is securely communicated across healthcare enterprises.
-
E.
Xue
Xue is a Chinese surname borne by various notable historical and contemporary figures.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c68811dd1c8190ac460bb39e64e1f0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6e9dc835881909ea646c392a980b6 |
completed | March 27, 2026, 8:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7cc17a3788190842a852fb4b96185 |
completed | March 28, 2026, 12:39 p.m. |
Created at: March 27, 2026, 2:54 p.m.