Triple
T32445052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Rats |
E829119
|
entity |
| Predicate | hasApproximateNumberOfRats |
P192071
|
FINISHED |
| Object | 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: thousands | Statement: [Temple of Rats, hasApproximateNumberOfRats, thousands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateNumberOfRats Context triple: [Temple of Rats, hasApproximateNumberOfRats, thousands]
-
A.
hasApproximateNumberOfMonkeys
Indicates that an entity is associated with an estimated or non-exact count of monkeys.
-
B.
hasApproximateNumberOfResponsa
Indicates that an entity is associated with a rough or estimated count of responsa, rather than an exact number.
-
C.
mineCountApproximate
Indicates that the number of mines associated with an entity is estimated or roughly counted rather than known exactly.
-
D.
approximateNumberOfZebra
Indicates that one entity specifies an estimated or approximate count of zebras associated with another entity.
-
E.
hasApproximateNumberOfPeople
Indicates that an entity is associated with an estimated or approximate count of people, rather than an exact number.
- 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69fcf36bb86c8190a0a0ccf47cb56e5c |
completed | May 7, 2026, 8:17 p.m. |
Created at: May 1, 2026, 12:55 a.m.