Triple
T16702852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XUL |
E405892
|
entity |
| Predicate | usedToBuild |
P64282
|
FINISHED |
| Object | Firefox browser chrome |
—
|
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: Firefox browser chrome | Statement: [XUL, usedToBuild, Firefox browser chrome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToBuild Context triple: [XUL, usedToBuild, Firefox browser chrome]
-
A.
usedOnBuildingOf
Indicates that something is applied to, installed on, or otherwise utilized on the structure of a particular building.
-
B.
constructionUsed
chosen
Indicates that one entity was employed as a construction method, material, or component in creating or assembling another entity.
-
C.
builtFrom
Indicates that one entity is constructed, composed, or formed using another entity as its material, component, or source.
-
D.
usesBuilding
Indicates that one entity makes use of, occupies, or operates within a particular building.
-
E.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e38333a6908190a17d2dee2ca622d6 |
completed | April 18, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.