Triple
T17675768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ERB |
E440638
|
entity |
| Predicate | supportsScriptTag |
P82712
|
FINISHED |
| Object | <% %> |
—
|
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: <% %> | Statement: [ERB, supportsScriptTag, <% %>]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsScriptTag Context triple: [ERB, supportsScriptTag, <% %>]
-
A.
containsScript
Indicates that one entity includes or embeds the script of another entity within it.
-
B.
scriptSupport
chosen
Indicates that one entity provides or enables scripting capabilities or support for another entity.
-
C.
scriptElement
Indicates that one entity is a script element (such as code or instructions) that is embedded in or associated with another entity, typically a document or resource.
-
D.
addsScript
Indicates that one entity attaches or incorporates a script (code or instructions) into another entity, enabling additional behavior or functionality.
-
E.
usesScriptDerivedFrom
Indicates that one entity employs a writing system that is historically or structurally derived from the script used by another entity.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f6cca54819094ea0bed1517724e |
completed | April 19, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10 a.m.