Triple
T28998554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jakarta Standard Tag Library |
E736228
|
entity |
| Predicate | tagPrefixExample |
P127789
|
FINISHED |
| Object | c |
—
|
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: c | Statement: [Jakarta Standard Tag Library, tagPrefixExample, c]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tagPrefixExample Context triple: [Jakarta Standard Tag Library, tagPrefixExample, c]
-
A.
tagPrefix
Indicates that one tag string serves as the starting substring (prefix) of another tag string in a tagging or labeling context.
-
B.
addressExamplePrefix
Indicates that an address example is introduced or categorized by a specific prefix string used to distinguish or group it.
-
C.
namespacePrefix
Indicates the abbreviated prefix string associated with a particular namespace URI in a naming or identifier system.
-
D.
namePrefix
Indicates that one entity is a prefix or leading part of another entity’s name.
-
E.
platformTagExample
chosen
Indicates that a specific example is provided to illustrate or clarify how a particular platform tag is used or applied.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fb8003081909d0e3ee34237bc29 |
completed | May 2, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:33 a.m.