Triple
T20885049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | linear logic |
E514255
|
entity |
| Predicate | hasConnective |
P51086
|
FINISHED |
| Object | multiplicative conjunction |
—
|
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: multiplicative conjunction | Statement: [linear logic, hasConnective, multiplicative conjunction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConnective Context triple: [linear logic, hasConnective, multiplicative conjunction]
-
A.
hasConnector
Indicates that one entity is linked or joined to another entity through a connector or connecting element.
-
B.
hasConjunction
chosen
Indicates that two or more entities are linked together by a coordinating conjunction, forming a combined or joint relationship.
-
C.
hasConjunctForms
Indicates that an entity is associated with one or more conjunct (combined or compound) forms of itself or related elements.
-
D.
hasCoupling
Indicates that two entities are linked or joined together in a way that allows them to interact, transfer, or coordinate motion, energy, or information.
-
E.
junctionOf
Indicates that one or more entities meet or intersect at a common point, forming a junction between them.
- 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c67c9d1c81908031eb77c124f119 |
completed | April 21, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:46 p.m.