Triple
T34614759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Python 3.x |
E888831
|
entity |
| Predicate | defaultStringType |
P90867
|
FINISHED |
| Object | Unicode string |
—
|
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: Unicode string | Statement: [Python 3.x, defaultStringType, Unicode string]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultStringType Context triple: [Python 3.x, defaultStringType, Unicode string]
-
A.
primaryStringTypeFor
chosen
Indicates that one entity serves as the main or default string type associated with another entity.
-
B.
defaultValue
Indicates that one entity serves as the pre-assigned or fallback value automatically used for another entity when no explicit value is provided.
-
C.
stringTypes
Indicates that the subject and object are related through specific string data types or classifications of string values.
-
D.
defaultNameValue
Indicates that an entity is assigned a standard or fallback name value used when no specific name has been provided.
-
E.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 1, 2026, 2:03 a.m.