Triple
T4485683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faraday effect |
E107232
|
entity |
| Predicate | isNonreciprocal |
P26667
|
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: [Faraday effect, isNonreciprocal, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonreciprocal Context triple: [Faraday effect, isNonreciprocal, true]
-
A.
nonExclusive
Indicates that the relationship or access is shared among multiple parties and is not limited to a single, exclusive holder.
-
B.
isNonJudicial
Indicates that an action, process, or decision occurs outside of formal judicial proceedings and is not carried out by a court or judge.
-
C.
isOneWay
chosen
Indicates that the relationship or action proceeds in only one direction from a source entity to a target entity, without a corresponding reverse relation.
-
D.
nonTransferable
Indicates that a right, asset, or privilege cannot be legally or contractually transferred from one party to another.
-
E.
notTransmittedBy
Indicates that a particular entity does not serve as a carrier or medium through which something (such as a disease, signal, or information) is passed from one entity to another.
- 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_69bd43f84f788190a1383579c4a595be |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd556d29f08190bab1e872dd7e819f |
completed | March 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69bd5213e3d0819094b026989e686f01 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 12:59 p.m.