Triple
T22650133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JSX |
E559068
|
entity |
| Predicate | defaultAttributeNameForCSS |
P149063
|
FINISHED |
| Object | className |
—
|
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: className | Statement: [JSX, defaultAttributeNameForCSS, className]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultAttributeNameForCSS Context triple: [JSX, defaultAttributeNameForCSS, className]
-
A.
defaultNameValue
Indicates that an entity is assigned a standard or fallback name value used when no specific name has been provided.
-
B.
nameStyle
Indicates how an entity’s name is formatted or stylistically presented (e.g., capitalization, punctuation, or naming convention).
-
C.
exportName
Indicates that one entity is exported under a specific name or label in relation to another context or system.
-
D.
givenNameFor
Indicates that one entity is the personal first name assigned to or used for another entity.
-
E.
namePrefix
Indicates that one entity is a prefix or leading part of another entity’s name.
- 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1703b40b88190aec5cf2fa28bfcbf |
completed | April 29, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:05 p.m.