Triple
T31264548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Führerhauptquartiere |
E797216
|
entity |
| Predicate | numberOfKnownSites |
P14032
|
FINISHED |
| Object | more than a dozen |
—
|
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: more than a dozen | Statement: [Führerhauptquartiere, numberOfKnownSites, more than a dozen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfKnownSites Context triple: [Führerhauptquartiere, numberOfKnownSites, more than a dozen]
-
A.
numberOfSites
chosen
Indicates the total count of distinct sites associated with or involved in the given entity or context.
-
B.
numberOfKnownMembers
Indicates the count of members within a group or set whose identities are known or have been explicitly determined.
-
C.
hasMemorySites
Indicates that an entity is associated with one or more specific locations where memories or memory-related information are stored or maintained.
-
D.
numberOfArchaeologicalSites
Indicates the total count of archaeological sites associated with a given entity or context.
-
E.
numberOfHosts
Indicates the total count of distinct hosts associated with or involved in a given entity or event.
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00ca5e907481909d391afd55938a1b |
completed | May 10, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_6a00ca2214348190a674a85ede709e2e |
completed | May 10, 2026, 6:10 p.m. |
Created at: April 29, 2026, 9:12 p.m.