Triple
T5296673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mormon pioneers |
E119873
|
entity |
| Predicate | estimatedNumber |
P56974
|
FINISHED |
| Object | tens of thousands |
—
|
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: tens of thousands | Statement: [Mormon pioneers, estimatedNumber, tens of thousands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedNumber Context triple: [Mormon pioneers, estimatedNumber, tens of thousands]
-
A.
estimatedMemberCount
chosen
Indicates the approximate or predicted number of members associated with an entity.
-
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.
employsApproximateNumberOfPeople
Indicates that an entity employs a roughly estimated or approximate number of people, rather than an exact headcount.
-
E.
approximateNumberAwarded
Indicates the estimated quantity of awards or recognitions given in a particular context 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_69bd446f22b88190b6a47fb91c68a3e7 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8e44e7c881909b241b2fec366038 |
completed | March 20, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69bd845097ac81909678624c4907fda4 |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:53 p.m.