Triple
T3420450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iron Browser |
E72102
|
entity |
| Predicate | hasUpdateModel |
P19968
|
FINISHED |
| Object | periodic manual updates |
—
|
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: periodic manual updates | Statement: [Iron Browser, hasUpdateModel, periodic manual updates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUpdateModel Context triple: [Iron Browser, hasUpdateModel, periodic manual updates]
-
A.
isUpdated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or a reference point.
-
B.
hasEditingModel
Indicates that one entity is associated with another entity that serves as its editing or modification model.
-
C.
isUpdatedThrough
Indicates that one entity’s state or content is modified or brought up to date as a result of a process, action, or interaction involving another entity.
-
D.
hasReleaseModel
chosen
Indicates the type or strategy of release associated with an entity, such as how or under what model it is made available.
-
E.
hasComponentModel
Indicates that an entity includes or is associated with a specific component model as part of its structure or configuration.
- 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb94eb9e8819087a525df4550914b |
completed | March 8, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69adadfea024819094b41a13bc004bda |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.