Triple
T1612206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trident layout engine |
E34637
|
entity |
| Predicate | proprietary |
P27024
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Trident layout engine, proprietary, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proprietary Context triple: [Trident layout engine, proprietary, true]
-
A.
wasProprietaryUntil
Indicates that something was owned or controlled as proprietary (not publicly available or open) up to a specified point in time.
-
B.
property
Indicates that one entity possesses, is characterized by, or has an attribute or quality associated with another entity.
-
C.
hasProprietaryStatus
chosen
Indicates that something is owned, controlled, or protected as proprietary rather than being public or freely available.
-
D.
protectedIn
Indicates that one entity is safeguarded, preserved, or kept safe within the context, environment, or jurisdiction of another entity.
-
E.
publicOrPrivate
Indicates whether something is designated as publicly accessible or restricted to private use or access.
- 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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93fa6926081908bc78d15c0be3185 |
completed | March 5, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69a907c35f848190a2428c52e81d013e |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.