Triple
T38228794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | How Great Thou Art |
E1012227
|
entity |
| Predicate | countryOfSignificantUse |
P202497
|
FINISHED |
| Object | United States |
E14
|
NE 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: United States | Statement: [How Great Thou Art, countryOfSignificantUse, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryOfSignificantUse Context triple: [How Great Thou Art, countryOfSignificantUse, United States]
-
A.
countryOfSymbolicUse
Indicates the country in which something (such as a symbol, object, or element) is used in a symbolic or representative way.
-
B.
primaryUseCountry
Indicates the country in which something is primarily used or most commonly utilized.
-
C.
notableUseCountry
chosen
Indicates that something is notably or prominently used within a particular country.
-
D.
secondaryCountryOfUse
Indicates that an entity is used or applied in a country that is not its primary country of use but serves as an additional or secondary location of use.
-
E.
usedByCountriesWith
Indicates that something (such as an item, system, or practice) is utilized or employed by one or more specified countries in common.
- F. None of above.
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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41853578cc8190b6b0c5c20d8496a1 |
completed | June 28, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.