Triple
T29214480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eleventh United States decennial census |
E740627
|
entity |
| Predicate | precededByTechnology |
P59506
|
FINISHED |
| Object | manual tabulation |
—
|
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: manual tabulation | Statement: [Eleventh United States decennial census, precededByTechnology, manual tabulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precededByTechnology Context triple: [Eleventh United States decennial census, precededByTechnology, manual tabulation]
-
A.
laterUsedTechnology
Indicates that one entity adopted or employed a technology after another entity had already used it.
-
B.
developedBefore
Indicates that one entity was developed or created earlier in time than another entity.
-
C.
precededByUse
Indicates that one use, action, or event occurs earlier in time and is directly followed by another specified use, action, or event.
-
D.
formerTechnology
chosen
Indicates that an entity previously used or was associated with a particular technology but no longer is.
-
E.
wasEarlyAdopterOf
Indicates that an entity adopted, used, or supported something significantly earlier than most others.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 28, 2026, 12:12 p.m.