Triple
T6668510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode 4.1 |
E151664
|
entity |
| Predicate | addsProperty |
P3699
|
FINISHED |
| Object | Line_Break refinements |
—
|
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: Line_Break refinements | Statement: [Unicode 4.1, addsProperty, Line_Break refinements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsProperty Context triple: [Unicode 4.1, addsProperty, Line_Break refinements]
-
A.
changesProperty
Indicates that one entity causes a change in a specific property or attribute of another entity.
-
B.
providesProperty
chosen
Indicates that one entity supplies, grants, or makes a particular property or attribute available to another entity.
-
C.
modularProperty
Indicates that one entity possesses a characteristic, behavior, or component that is designed to be separable, interchangeable, or recombinable with others in a modular fashion.
-
D.
ownedProperty
Indicates that one entity possesses legal ownership or control over another entity as property.
-
E.
addedFor
Indicates that one entity was created, included, or introduced specifically for the benefit, use, or purpose of 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_69c687f71fc081909dbd45d6377f6045 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce738fe88190a5557900efeec7ec |
completed | March 27, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69c6ad09974c81908784300ae218961f |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:02 p.m.