Triple
T33607685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 11,000 Virgins |
E860903
|
entity |
| Predicate | possibleOriginalNumber |
P8195
|
FINISHED |
| Object | 11 |
—
|
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: 11 | Statement: [11,000 Virgins, possibleOriginalNumber, 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleOriginalNumber Context triple: [11,000 Virgins, possibleOriginalNumber, 11]
-
A.
possibleOriginalReference
Indicates that one entity may be the source, inspiration, or earlier version from which another entity is derived or referenced.
-
B.
estimatedOriginalLength
Indicates the approximated or inferred length that something originally had before any changes, damage, or loss.
-
C.
believedNumber
Indicates that one entity holds the belief that a certain numerical value correctly characterizes or applies to another entity or situation.
-
D.
originallyHad
Indicates that an entity previously possessed, contained, or was associated with something before a change, loss, or transformation occurred.
-
E.
number
chosen
Indicates that one entity is associated with a specific numerical value or count in relation to another entity or context.
- 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: May 1, 2026, 1:41 a.m.