Triple
T15801187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cairo Geniza fragments |
E383100
|
entity |
| Predicate | estimatedNumberOfItems |
P120121
|
FINISHED |
| Object | over 300000 fragments |
—
|
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: over 300000 fragments | Statement: [Cairo Geniza fragments, estimatedNumberOfItems, over 300000 fragments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedNumberOfItems Context triple: [Cairo Geniza fragments, estimatedNumberOfItems, over 300000 fragments]
-
A.
estimatedNumberOfRemains
Indicates the approximate count of human or other remains associated with an entity, based on estimation rather than an exact measurement.
-
B.
estimatedNumberOfBlocks
Indicates the approximate count of discrete blocks associated with or involved in the given entity or context.
-
C.
areEstimatedIn
Indicates that a value or quantity is approximated or inferred within a specified context, framework, or unit.
-
D.
sectionCountApproximate
Indicates that the number of sections associated with an entity is known only approximately rather than as an exact count.
-
E.
estimatedMemberCount
Indicates the approximate or predicted number of members associated with an entity.
- F. None of above. chosen
Provenance (4 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b522a2988190b2a2bde2da31b21e |
completed | April 16, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69e00e48d49c819081afccb02f9cf18b |
completed | April 15, 2026, 10:16 p.m. |
Created at: April 10, 2026, 4:48 a.m.