Triple
T33051966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LCD |
E845749
|
entity |
| Predicate | widelyAdoptedIn |
P11801
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [LCD, widelyAdoptedIn, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: widelyAdoptedIn Context triple: [LCD, widelyAdoptedIn, 1990s]
-
A.
widelyUsedIn
chosen
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
-
B.
isWidelyUsed
Indicates that something is commonly or extensively utilized across many contexts, users, or situations.
-
C.
isFamouslyUsedBy
Indicates that something is widely and notably used by a particular person, group, or entity, in a way that is broadly recognized or associated with them.
-
D.
usedByCountriesWith
Indicates that something (such as an item, system, or practice) is utilized or employed by one or more specified countries in common.
-
E.
laterAdoptedIn
Indicates that one entity was adopted, implemented, or taken up in another entity at a subsequent time relative to some earlier reference point or context.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:24 a.m.