Triple
T9767718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .net |
E237037
|
entity |
| Predicate | transferable |
P90522
|
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: [.net, transferable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferable Context triple: [.net, transferable, true]
-
A.
nonTransferable
Indicates that a right, asset, or privilege cannot be legally or contractually transferred from one party to another.
-
B.
transferableDuringLifetime
Indicates that the rights, ownership, or benefits associated with something can be legally transferred from one party to another while the original holder is still alive.
-
C.
isTransferableByPossession
Indicates that the rights or ownership associated with something can be transferred simply by transferring physical possession of it.
-
D.
transferFeature
Indicates a relationship where a feature, attribute, or capability is moved or reassigned from one entity to another.
-
E.
transferAgreement
Indicates a formal arrangement in which ownership, rights, or responsibilities are transferred from one party to another.
- F. None of above. chosen
Provenance (4 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_69ca84d831b8819090322686b47887ce |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda0a2da648190836916a45d2998d7 |
completed | April 1, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd06aa8bc88190904be19c8953def8 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:25 p.m.