Triple
T30802757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Modeler |
E784414
|
entity |
| Predicate | dataExchangeWith |
P127948
|
FINISHED |
| Object | LightWave 3D Layout |
—
|
NE NERFINISHED |
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: LightWave 3D Layout | Statement: [Modeler, dataExchangeWith, LightWave 3D Layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataExchangeWith Context triple: [Modeler, dataExchangeWith, LightWave 3D Layout]
-
A.
supportsDataExchange
chosen
Indicates that one entity enables or facilitates the transfer or sharing of data with another entity.
-
B.
exchangeType
Indicates the kind or category of exchange occurring between entities, such as the method, direction, or nature of what is being traded or transferred.
-
C.
exchangeAuthority
Indicates a relationship where control or decision-making power is transferred or swapped between entities.
-
D.
isExchangedVia
Indicates that something is transferred or traded from one party to another through a specified medium, channel, or mechanism.
-
E.
dataTransferType
Indicates the method or mode by which data is transmitted or exchanged between entities.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6903c7bc48190b7c72ce16dd44987 |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:42 p.m.