Triple
T14569254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LZ 10 Schwaben |
E341865
|
entity |
| Predicate | registration |
P3328
|
FINISHED |
| Object | LZ 10 |
E341865
|
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: LZ 10 | Statement: [LZ 10 Schwaben, registration, LZ 10]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LZ 10 Context triple: [LZ 10 Schwaben, registration, LZ 10]
-
A.
LZ 37
LZ 37 was an early German military Zeppelin airship used during World War I, known for its role in some of the first strategic bombing raids and for being among the earliest airships shot down in combat.
-
B.
LZ 10 Schwaben
chosen
LZ 10 Schwaben was an early 20th-century German passenger-carrying Zeppelin airship known for pioneering commercial air travel before World War I.
-
C.
LZ 38
LZ 38 was a German World War I Zeppelin airship best known for conducting some of the earliest strategic bombing raids on London.
-
D.
LZ 18 Sachsen
LZ 18 Sachsen was an early German Zeppelin passenger airship used in the 1910s, notable for its role in advancing rigid airship design and operations before World War I.
-
E.
LZ-2
LZ-2 is a designated rocket landing site used for the controlled return and recovery of launch vehicles.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb3f2121481908f2385637944785d |
completed | April 14, 2026, 9:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd94b4013881908fddb8b3cf8494de |
completed | May 8, 2026, 7:45 a.m. |
Created at: April 10, 2026, 1:23 a.m.